Lines Matching full:are
13 There are many cases where an asynchronous process execution context
22 While there are work items on the workqueue the worker executes the
82 worker threads become idle. These worker threads are managed in so
89 There are two worker-pools, one for normal work items and the other
96 aspects of the way the work items are executed by setting flags on the
97 workqueue they are putting the work item on. These flags include
110 (how many execution contexts are active) is an important issue. cmwq
118 number of the currently runnable workers. Generally, work items are
121 stalling should be optimal. As long as there are one or more runnable
125 are pending work items. This allows using a minimal number of workers
141 more execution contexts are necessary, which in turn is guaranteed
143 on code paths that handle memory reclaim are required to be queued on
153 ``create_*workqueue()`` functions are deprecated and scheduled for
160 and ``@max_active`` control how work items are assigned execution
168 Work items queued to an unbound wq are served by the special
169 worker-pools which host workers which are not bound to any
186 suspend operations. Work items on the wq are drained and no
195 Work items of a highpri wq are queued to the highpri
196 worker-pool of the target cpu. Highpri worker-pools are
208 work items which are expected to hog CPU cycles so that their
220 workqueues are now non-reentrant - any work item is guaranteed to be
235 ``num_possible_cpus()``. These values are chosen sufficiently high
236 such that they are not the limiting factor while providing protection
262 Work items w0, w1, w2 are queued to a bound wq q0 on the same CPU.
311 Now, let's assume w1 and w2 are queued to a different wq q1 which has
330 items which are used during memory reclaim. Each wq with
344 which are not involved in memory reclaim and don't need to be
350 * Unless work items are expected to consume a huge amount of CPU
358 Because the work functions are executed by generic worker threads
359 there are a few tricks needed to shed some light on misbehaving
369 If kworkers are going crazy (using too much cpu), there are two types