Documentation/core-api/workqueue.rst

13 There are many cases where an asynchronous process execution context
17 When such an asynchronous execution context is needed, a work item
19 independent thread serves as the asynchronous execution context.  The
42 worker pool.  An MT wq could provide only one execution context per CPU
44 those very limited execution contexts leading to various problems
45 including proneness to deadlocks around the single execution context.
71 In order to ease the asynchronous execution of functions a new
97 concurrent execution context, there's no need to worry about concurrency.
99 the BH execution context. A BH workqueue can be considered a convenience
118 (how many execution contexts are active) is an important issue.  cmwq
130 workers on the CPU, the worker-pool doesn't start execution of a new
134 without losing execution bandwidth.
149 more execution contexts are necessary, which in turn is guaranteed
152 wq's that have a rescue-worker reserved for execution under memory
154 for execution contexts to free up.
166 A wq no longer manages execution resources but serves as a domain for
168 and ``@max_active`` control how work items are assigned execution
189   specific CPU.  This makes the wq behave as a simple execution
191   worker-pools try to start execution of work items as soon as
206   new work item starts execution until thawed.
211   execution context regardless of memory pressure.
226   worker-pool from starting execution.  This is useful for bound
228   execution is regulated by the system scheduler.
233   non-CPU-intensive work items can delay execution of CPU
242 ``@max_active`` determines the maximum number of execution contexts per
259 Some users depend on strict execution ordering where only one work item
269 The following example execution scenarios try to illustrate how cmwq
341   ``WQ_MEM_RECLAIM`` set has an execution context reserved for it.  If
357   difference in execution characteristics between using a dedicated wq
362   level of locality in wq operations and work item execution.
419   item starts execution, workqueue makes a best-effort attempt to ensure
464 execution locality matter between the issuer and ``kcryptd``. The following