Subversion Repositories HelenOS-doc

Rev

Rev 40 | Rev 48 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
9 bondari 1
<?xml version="1.0" encoding="UTF-8"?>
39 bondari 2
<chapter id="architecture">
3
  <?dbhtml filename="arch.html"?>
9 bondari 4
 
39 bondari 5
  <title>Architecture overview</title>
37 bondari 6
 
39 bondari 7
  <section>
45 jermar 8
    <para>
9
      <mediaobject id="arch1">
39 bondari 10
        <imageobject role="html">
11
          <imagedata fileref="images/arch1.png" format="PNG" />
12
        </imageobject>
38 bondari 13
 
39 bondari 14
        <imageobject role="fop">
15
          <imagedata fileref="images.vector/arch1.svg" format="SVG" />
16
        </imageobject>
45 jermar 17
      </mediaobject>
18
    </para>
39 bondari 19
  </section>
38 bondari 20
 
39 bondari 21
  <section>
45 jermar 22
    <para>The HelenOS operating system is designed as a relatively small
23
    microkernel assisted with a set of userspace drivers and server tasks.
24
    HelenOS is not very radical in what subsystems should or should not be
25
    implemented in the kernel - in some cases, both kernel and userspace
26
    drivers exist. The reason for creating the system as a microkernel is
27
    prosaic. Even though it is initially more difficult to get the same level
28
    of functionality from a microkernel than it is in the case of a simple
29
    monolithic kernel, a microkernel is much easier to maintain once the
30
    pieces have been put to work together. Therefore, the kernel of HelenOS,
31
    as well as the essential userspace libraries thereof can be maintained by
32
    only a few developers who understand them completely. In addition, a
33
    microkernel based operating system reaches completion sooner than
34
    monolithic kernels as the system can be used even without some traditional
35
    subsystems (e.g. block devices, filesystems and networking).</para>
38 bondari 36
 
45 jermar 37
    <para>HelenOS is comprised of the kernel and userspace server tasks. The
38
    kernel provides scheduling, memory management and IPC. It also contains
39
    essential device drivers that control the system clock and other devices
40
    necessary to guarantee a safe environment. Userspace communicates with the
41
    kernel through </para>
39 bondari 42
  </section>
43
</chapter>