Lines Matching refs:thread

190 the main thread, queued up in a thread pool and completed when the main thread deems they are
195 (e.g. locking and pushing a buffer), it waits for the main thread to complete it using an Event
196 object. The main thread holds a queue of these Event objects and completes the
197 corresponding Event base on its time stamp. After completing an increment, the main thread will
200 The main thread's execution flow is outlined below
213 A worker thread's flow looks like so
231 - **Waiting** - The worker is waiting on the main thread to signal it.
232 - **Signaled** - The worker has just been signaled by the main thread
235 When the main thread wants to finish the execution of a worker, the worker can either still be
236 **SettingUp**, in which the main thread will wait, or the worker will be **Waiting**, in which the
237 main thread will **Signal** it to complete. The worker thread changes itself to the **Running**
238 state once **Signaled**. This last step exists in order to communicate back to the main thread that
239 the worker thread has actually started completing its execution, rather than being preempted right
240 after signalling. Once this happens, the main thread schedules the next worker. This makes sure
244 worker and main thread respectively.
248 During a **BuferUpdate**, the worker thread will wait until **Signaled** to unlock and post a