Lines Matching refs:items
29 While there are work items on the workqueue the worker executes the
30 functions associated with the work items one after the other. When
49 while a ST wq one for the whole system. Work items had to compete for
91 subsystems and drivers queue work items on and the backend mechanism
92 which manages worker-pools and processes the queued work items.
94 There are two worker-pools, one for normal work items and the other
96 worker-pools to serve work items queued on unbound workqueues - the
99 Subsystems and drivers can create and queue work items through special
101 aspects of the way the work items are executed by setting flags on the
123 number of the currently runnable workers. Generally, work items are
130 are pending work items. This allows using a minimal number of workers
147 through the use of rescue workers. All work items which might be used
164 and @max_active control how work items are assigned execution
171 Work items queued to an unbound wq are served by the special
175 worker-pools try to start execution of work items as soon as
190 suspend operations. Work items on the wq are drained and no
201 Work items of a highpri wq are queued to the highpri
211 Work items of a CPU intensive wq do not contribute to the
213 work items will not prevent other work items in the same
215 work items which are expected to hog CPU cycles so that their
218 Although CPU intensive work items don't contribute to the
221 non-CPU-intensive work items can delay execution of CPU
222 intensive work items.
233 CPU which can be assigned to the work items of a wq. For example,
234 with @max_active of 16, at most 16 work items of the wq can be
243 The number of active work items of a wq is usually regulated by the
244 users of the wq, more specifically, by how many work items the users
246 throttling the number of active work items, specifying '0' is
251 behavior. Work items on such wq are always queued to the unbound
261 Work items w0, w1, w2 are queued to a bound wq q0 on the same CPU.
327 * Do not forget to use WQ_MEM_RECLAIM if a wq may process work items
330 dependency among multiple work items used during memory reclaim,
340 (WQ_MEM_RECLAIM, flush and work item attributes. Work items which
342 part of a group of work items, and don't require any special
347 * Unless work items are expected to consume a huge amount of CPU