1 | \makeglossaries
|
---|
2 |
|
---|
3 | \longnewglossaryentry{callsite-locking}
|
---|
4 | {name={callsite-locking}}
|
---|
5 | {
|
---|
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 | }
|
---|
8 |
|
---|
9 | \longnewglossaryentry{entry-point-locking}
|
---|
10 | {name={entry-point-locking}}
|
---|
11 | {
|
---|
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 | }
|
---|
14 |
|
---|
15 | \longnewglossaryentry{bulk-acq}
|
---|
16 | {name={bulk-acquiring}}
|
---|
17 | {
|
---|
18 | Implicitly acquiring several monitors when entering a monitor.
|
---|
19 | }
|
---|
20 |
|
---|
21 | \longnewglossaryentry{multi-acq}
|
---|
22 | {name={multiple-acquisition}}
|
---|
23 | {
|
---|
24 | Any locking technique that allows a single thread to acquire the same lock multiple times.
|
---|
25 | }
|
---|
26 |
|
---|
27 | \longnewglossaryentry{mon-ctx}
|
---|
28 | {name={monitor context}}
|
---|
29 | {
|
---|
30 | The state of the current thread regarding which monitors are owned.
|
---|
31 | }
|
---|
32 |
|
---|
33 |
|
---|
34 | \longnewglossaryentry{uthread}
|
---|
35 | {name={user-level thread}}
|
---|
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 invisible 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 | {
|
---|
45 | Threads 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 | {
|
---|
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 |
|
---|
55 | \textit{Synonyms : Tasks.}
|
---|
56 | }
|
---|
57 |
|
---|
58 | \longnewglossaryentry{job}
|
---|
59 | {name={job}}
|
---|
60 | {
|
---|
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 |
|
---|
63 | \textit{Synonyms : Tasks.}
|
---|
64 | }
|
---|
65 |
|
---|
66 | \longnewglossaryentry{pool}
|
---|
67 | {name={thread-pool}}
|
---|
68 | {
|
---|
69 | Group of homogeneuous threads that loop executing units of works after another.
|
---|
70 |
|
---|
71 | \textit{Synonyms : }
|
---|
72 | }
|
---|
73 |
|
---|
74 | \longnewglossaryentry{cfacluster}
|
---|
75 | {name={cluster}}
|
---|
76 | {
|
---|
77 | A group of \gls{kthread} executed in isolation.
|
---|
78 |
|
---|
79 | \textit{Synonyms : None.}
|
---|
80 | }
|
---|
81 |
|
---|
82 | \longnewglossaryentry{cfathread}
|
---|
83 | {name={thread}}
|
---|
84 | {
|
---|
85 | User level threads that are the default in \CFA. Generally declared using the \code{thread} keyword.
|
---|
86 |
|
---|
87 | \textit{Synonyms : None.}
|
---|
88 | }
|
---|
89 |
|
---|
90 | \longnewglossaryentry{preemption}
|
---|
91 | {name={preemption}}
|
---|
92 | {
|
---|
93 | Involuntary context switch imposed on threads at a specified rate.
|
---|
94 |
|
---|
95 | \textit{Synonyms : None.}
|
---|
96 | }
|
---|
97 |
|
---|
98 | \newacronym{tls}{TLS}{Thread Local Storage}
|
---|
99 | \newacronym{api}{API}{Application Program Interface}
|
---|
100 | \newacronym{raii}{RAII}{Resource Acquisition Is Initialization}
|
---|
101 | \newacronym{numa}{NUMA}{Non-Uniform Memory Access}
|
---|