Lines Matching refs:worker
20 queue is called workqueue and the thread is called worker.
22 While there are work items on the workqueue the worker executes the
24 there is no work item left on the workqueue the worker becomes idle.
25 When a new work item gets queued, the worker begins executing again.
32 worker thread per CPU and a single threaded (ST) wq had one worker
42 worker pool. An MT wq could provide only one execution context per CPU
60 * Use per-CPU unified worker pools shared by all wq to provide
64 * Automatically regulate worker pool and level of concurrency so that
84 the worker threads become idle. These worker threads are managed in
85 worker-pools.
89 which manages worker-pools and processes the queued work items.
91 There are two worker-pools, one for normal work items and the other
93 worker-pools to serve work items queued on unbound workqueues - the
98 Each per-CPU BH worker pool contains only one pseudo worker which represents
110 When a work item is queued to a workqueue, the target worker-pool is
112 and appended on the shared worklist of the worker-pool. For example,
114 be queued on the worklist of either normal or highpri worker-pool that
123 Each worker-pool bound to an actual CPU implements concurrency
124 management by hooking into the scheduler. The worker-pool is notified
125 whenever an active worker wakes up or sleeps and keeps track of the
130 workers on the CPU, the worker-pool doesn't start execution of a new
131 work, but, when the last running worker goes to sleep, it immediately
132 schedules a new worker so that the CPU doesn't sit idle while there
143 backing worker pools matching the attributes. The responsibility of
152 wq's that have a rescue-worker reserved for execution under memory
153 pressure. Else it is possible that the worker-pool deadlocks waiting
188 worker-pools which host workers which are not bound to any
191 worker-pools try to start execution of work items as soon as
215 worker-pool of the target cpu. Highpri worker-pools are
216 served by worker threads with elevated nice level.
218 Note that normal and highpri worker-pools don't interact with
226 worker-pool from starting execution. This is useful for bound
371 boundaries. A work item queued on the workqueue will be assigned to a worker
373 Once started, the worker may or may not be allowed to move outside the scope
384 worker on the same CPU. This makes unbound workqueues behave as per-cpu
420 that the worker is inside its affinity scope, which is called
421 repatriation. Once started, the scheduler is free to move the worker
611 configuration, worker pools and how workqueues map to the pools: ::
718 Because the work functions are executed by generic worker threads
747 the stack trace of the offending worker thread. ::
766 executed by at most one worker system-wide at any given time.