source: doc/proposals/concurrency/annex/glossary.tex @ 3364962

aaron-thesisarm-ehcleanup-dtorsdeferred_resndemanglerjacob/cs343-translationjenkins-sandboxnew-astnew-ast-unique-exprnew-envno_listpersistent-indexerresolv-newwith_gc
Last change on this file since 3364962 was 3364962, checked in by Thierry Delisle <tdelisle@…>, 4 years ago

Updated concurrency draft and added new section for implementation.

  • Property mode set to 100644
File size: 2.7 KB
Line 
1\makeglossaries
2
3\longnewglossaryentry{callsite-locking}
4{name={callsite-locking}}
5{
6Locking 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}
8
9\longnewglossaryentry{entry-point-locking}
10{name={entry-point-locking}}
11{
12Locking 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}
14
15\longnewglossaryentry{bulk-acq}
16{name={bulk-acquiring}}
17{
18Implicitly acquiring several monitors when entering a monitor.
19}
20
21\longnewglossaryentry{multi-acq}
22{name={multiple-acquisition}}
23{
24Any locking technique which allow any single thread to acquire a lock multiple times.
25}
26
27\longnewglossaryentry{mon-ctx}
28{name={monitor context}}
29{
30The state of the current thread regarding which monitors are owned.
31}
32
33
34\longnewglossaryentry{uthread}
35{name={user-level thread}}
36{
37Threads 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
39\textit{Synonyms : User threads, Lightweight threads, Green threads, Virtual threads, Tasks.}
40}
41
42\longnewglossaryentry{kthread}
43{name={kernel-level thread}}
44{
45Threads created and managed inside kernel-space. Each thread has its own stack and its own thread of execution. Kernel-level threads are owned, managed and scheduled by the underlying operating system.
46
47\textit{Synonyms : OS threads, Hardware threads, Physical threads.}
48}
49
50\longnewglossaryentry{fiber}
51{name={fiber}}
52{
53Fibers 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
55\textit{Synonyms : Tasks.}
56}
57
58\longnewglossaryentry{job}
59{name={job}}
60{
61Unit 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
63\textit{Synonyms : Tasks.}
64}
65
66\longnewglossaryentry{pool}
67{name={thread-pool}}
68{
69Group of homogeneuous threads that loop executing units of works after another.
70
71\textit{Synonyms : }
72}
73
74\longnewglossaryentry{cfacluster}
75{name={cluster}}
76{
77TBD...
78
79\textit{Synonyms : None.}
80}
81
82\longnewglossaryentry{cfacpu}
83{name={processor}}
84{
85TBD...
86
87\textit{Synonyms : None.}
88}
89
90\longnewglossaryentry{cfathread}
91{name={thread}}
92{
93TBD...
94
95\textit{Synonyms : None.}
96}
97
98\longnewglossaryentry{preemption}
99{name={preemption}}
100{
101TBD...
102
103\textit{Synonyms : None.}
104}
105
106\newacronym{tls}{TLS}{Thread Local Storage}
107\newacronym{api}{API}{Application Program Interface}
108\newacronym{raii}{RAII}{Ressource Acquisition Is Initialization}
109\newacronym{numa}{NUMA}{Non-Uniform Memory Access}
Note: See TracBrowser for help on using the repository browser.