source: doc/proposals/concurrency/glossary.tex @ d02aaa9

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

Update intro up to internal scheduling

  • Property mode set to 100644
File size: 2.4 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{group-acquire}
16{name={bulked acquiring}}
17{
18Implicitly acquiring several monitors when entering a monitor.
19}
20
21
22\longnewglossaryentry{uthread}
23{name={user-level thread}}
24{
25Threads 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.
26
27\textit{Synonyms : User threads, Lightweight threads, Green threads, Virtual threads, Tasks.}
28}
29
30\longnewglossaryentry{kthread}
31{name={kernel-level thread}}
32{
33Threads 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.
34
35\textit{Synonyms : OS threads, Hardware threads, Physical threads.}
36}
37
38\longnewglossaryentry{fiber}
39{name={fiber}}
40{
41Fibers 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.
42
43\textit{Synonyms : Tasks.}
44}
45
46\longnewglossaryentry{job}
47{name={job}}
48{
49Unit 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.
50
51\textit{Synonyms : Tasks.}
52}
53
54\longnewglossaryentry{pool}
55{name={thread-pool}}
56{
57Group of homogeneuous threads that loop executing units of works after another.
58
59\textit{Synonyms : }
60}
61
62\longnewglossaryentry{cfacluster}
63{name={cluster}}
64{
65TBD...
66
67\textit{Synonyms : None.}
68}
69
70\longnewglossaryentry{cfacpu}
71{name={processor}}
72{
73TBD...
74
75\textit{Synonyms : None.}
76}
77
78\longnewglossaryentry{cfathread}
79{name={thread}}
80{
81TBD...
82
83\textit{Synonyms : None.}
84}
85
86\longnewglossaryentry{preemption}
87{name={preemption}}
88{
89TBD...
90
91\textit{Synonyms : None.}
92}
93
94\newacronym{tls}{TLS}{Thread Local Storage}
95\newacronym{api}{API}{Application Program Interface}
96\newacronym{raii}{RAII}{Ressource Acquisition Is Initialization}
Note: See TracBrowser for help on using the repository browser.