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