/[hurd]/hurd-l4/doc/threads-tasks.tex
ViewVC logotype

Diff of /hurd-l4/doc/threads-tasks.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.1 by neal, Sun Sep 7 21:49:29 2003 UTC revision 1.2 by marcus, Sun Sep 7 22:24:06 2003 UTC
# Line 14  threads, and to destroy them. Line 14  threads, and to destroy them.
14    
15  The \texttt{task} server provides three different capability types.  The \texttt{task} server provides three different capability types.
16    
17  \subsubsection{Task control capabilities}  \paragraph{Task control capabilities}
18  If a new task is created, it is always associated with a task control  If a new task is created, it is always associated with a task control
19  capability.  The task control capability can be used to create and  capability.  The task control capability can be used to create and
20  destroy threads in the task, and destroy the task itself.  So the task  destroy threads in the task, and destroy the task itself.  So the task
# Line 31  that task. Line 31  that task.
31    capability reference is released.    capability reference is released.
32  \end{comment}  \end{comment}
33    
34  \subsubsection{Task info capabilities}  \paragraph{Task info capabilities}
35  \label{taskinfocap}  \label{taskinfocap}
36  Any task can create task info capabilities for other tasks.  Such task  Any task can create task info capabilities for other tasks.  Such task
37  info capabilities are used mainly in the IPC system (see section  info capabilities are used mainly in the IPC system (see section
# Line 74  capabilities for that task. Line 74  capabilities for that task.
74    do not need anymore.    do not need anymore.
75  \end{comment}  \end{comment}
76    
77  \subsubsection{Task manager capability}  \paragraph{Task manager capability}
78  A task is a relatively simple object, compared to a full blown POSIX  A task is a relatively simple object, compared to a full blown POSIX
79  process, for example.  As the \texttt{task} server is enforced system  process, for example.  As the \texttt{task} server is enforced system
80  code, the Hurd does not impose POSIX process semantics in the task  code, the Hurd does not impose POSIX process semantics in the task

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26