Lines Matching refs:execution

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
110 (how many execution contexts are active) is an important issue.  cmwq
122 workers on the CPU, the worker-pool doesn't start execution of a new
126 without losing execution bandwidth.
141 more execution contexts are necessary, which in turn is guaranteed
144 wq's that have a rescue-worker reserved for execution under memory
146 for execution contexts to free up.
158 A wq no longer manages execution resources but serves as a domain for
160 and ``@max_active`` control how work items are assigned execution
170   specific CPU.  This makes the wq behave as a simple execution
172   worker-pools try to start execution of work items as soon as
187   new work item starts execution until thawed.
192   execution context regardless of memory pressure.
207   worker-pool from starting execution.  This is useful for bound
209   execution is regulated by the system scheduler.
214   non-CPU-intensive work items can delay execution of CPU
223 ``@max_active`` determines the maximum number of execution contexts
241 Some users depend on the strict execution ordering of ST wq.  The
255 The following example execution scenarios try to illustrate how cmwq
327   ``WQ_MEM_RECLAIM`` set has an execution context reserved for it.  If
343   difference in execution characteristics between using a dedicated wq
348   level of locality in wq operations and work item execution.