51,7 → 51,9 |
maps to one kernel thread. Threads are grouped into tasks by functionality |
they provide (i.e. several threads implement functionality of one task). |
Tasks serve as containers of threads, they provide linkage to address |
space and are communication endpoints for IPC.</para> |
space and are communication endpoints for IPC. Finally, tasks can be |
holders of capabilities that entitle them to do certain sensitive |
operations (e.g access raw hardware and physical memory).</para> |
|
<para>The scheduler deploys several run queues on each processor. A thread |
ready for execution is put into one of the run queues, depending on its |
109,6 → 111,4 |
tasks. Calls can be synchronous or asynchronous and can be forwarded from |
one task to another.</para> |
</section> |
|
|
</chapter> |