- File:
-
- 1 edited
-
doc/proposals/concurrency/annex/glossary.tex (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/proposals/concurrency/annex/glossary.tex
rcf966b5 r3364962 4 4 {name={callsite-locking}} 5 5 { 6 Locking done by the calling routine. With this technique, a routine calling a monitor routine aquiresthe monitor \emph{before} making the call to the actuall routine.6 Locking done by the calling routine. With this technique, a routine calling a monitor routine will aquire the monitor \emph{before} making the call to the actuall routine. 7 7 } 8 8 … … 10 10 {name={entry-point-locking}} 11 11 { 12 Locking done by the called routine. With this technique, a monitor routine called by another routine aquiresthe monitor \emph{after} entering the routine body but prior to any other code.12 Locking done by the called routine. With this technique, a monitor routine called by another routine will aquire the monitor \emph{after} entering the routine body but prior to any other code. 13 13 } 14 14 … … 22 22 {name={multiple-acquisition}} 23 23 { 24 Any locking technique that allows a single thread to acquire the samelock multiple times.24 Any locking technique which allow any single thread to acquire a lock multiple times. 25 25 } 26 26 … … 35 35 {name={user-level thread}} 36 36 { 37 Threads created and managed inside user-space. Each thread has its own stack and its own thread of execution. User-level threads are in visible to the underlying operating system.37 Threads created and managed inside user-space. Each thread has its own stack and its own thread of execution. User-level threads are insisible to the underlying operating system. 38 38 39 39 \textit{Synonyms : User threads, Lightweight threads, Green threads, Virtual threads, Tasks.} … … 51 51 {name={fiber}} 52 52 { 53 Fibers are non-preemptive user-level threads. They share most of the caracteristics of user-level threads except that they cannot be preempted by an other fiber.53 Fibers are non-preemptive user-level threads. They share most of the caracteristics of user-level threads except that they cannot be preempted by an other fiber. 54 54 55 55 \textit{Synonyms : Tasks.} … … 59 59 {name={job}} 60 60 { 61 Unit of work, often sen t to a thread pool or worker pool to be executed. Has neither its own stack nor its own thread of execution.61 Unit of work, often send to a thread pool or worker pool to be executed. Has neither its own stack or its own thread of execution. 62 62 63 63 \textit{Synonyms : Tasks.} … … 75 75 {name={cluster}} 76 76 { 77 A group of \gls{kthread} executed in isolation. 77 TBD... 78 79 \textit{Synonyms : None.} 80 } 81 82 \longnewglossaryentry{cfacpu} 83 {name={processor}} 84 { 85 TBD... 78 86 79 87 \textit{Synonyms : None.} … … 83 91 {name={thread}} 84 92 { 85 User level threads that are the default in \CFA. Generally declared using the \code{thread} keyword.93 TBD... 86 94 87 95 \textit{Synonyms : None.} … … 91 99 {name={preemption}} 92 100 { 93 Involuntary context switch imposed on threads at a specified rate.101 TBD... 94 102 95 103 \textit{Synonyms : None.}
Note:
See TracChangeset
for help on using the changeset viewer.