Changeset 9c35431 for doc/proposals/concurrency/annex/glossary.tex
- Timestamp:
- Nov 29, 2017, 2:00:32 PM (6 years ago)
- Branches:
- ADT, arm-eh, ast-experimental, cleanup-dtors, enum, forall-pointer-decay, jacob/cs343-translation, jenkins-sandbox, master, new-ast, new-ast-unique-expr, pthread-emulation, qualifiedEnum
- Children:
- c13e8dc8
- Parents:
- c6e2c18 (diff), 389528b0 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/proposals/concurrency/annex/glossary.tex
rc6e2c18 r9c35431 4 4 {name={callsite-locking}} 5 5 { 6 Locking done by the calling routine. With this technique, a routine calling a monitor routine will aquirethe 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 aquires 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 will aquirethe 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 aquires 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 which allow any single thread to acquire alock multiple times.24 Any locking technique that allows a single thread to acquire the same 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 sisible 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 invisible 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 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 another fiber. 54 54 55 55 \textit{Synonyms : Tasks.} … … 59 59 {name={job}} 60 60 { 61 Unit of work, often sen d to a thread pool or worker pool to be executed. Has neither its own stackor its own thread of execution.61 Unit of work, often sent to a thread pool or worker pool to be executed. Has neither its own stack nor its own thread of execution. 62 62 63 63 \textit{Synonyms : Tasks.} … … 75 75 {name={cluster}} 76 76 { 77 TBD... 78 79 \textit{Synonyms : None.} 80 } 81 82 \longnewglossaryentry{cfacpu} 83 {name={processor}} 84 { 85 TBD... 77 A group of \gls{kthread} executed in isolation. 86 78 87 79 \textit{Synonyms : None.} … … 91 83 {name={thread}} 92 84 { 93 TBD...85 User level threads that are the default in \CFA. Generally declared using the \code{thread} keyword. 94 86 95 87 \textit{Synonyms : None.} … … 99 91 {name={preemption}} 100 92 { 101 TBD...93 Involuntary context switch imposed on threads at a specified rate. 102 94 103 95 \textit{Synonyms : None.}
Note: See TracChangeset
for help on using the changeset viewer.