Lines Matching refs:items

11 work items in a first in, first out manner. Each work item is processed by
21 * A **queue** of work items that have been added, but not yet processed.
23 * A **thread** that processes the work items in the queue. The priority of the
33 when no work items are available.
39    * Precise tracking of the status of cancelled work items, so that the
43    * Direct submission of delayable work items to the queue with
63 Any number of **work items** can be defined. Each work item is referenced
77 the preceding work items in its queue the thread will remove the next work
80 other items in the queue, a queued work item may be processed quickly or it
103 used with care, since the workqueue cannot process subsequent work items in
122 the processing of other work items in the workqueue's queue.
211     to submit new work items to the system workqueue, since each new workqueue
213     justified if it is not possible for its work items to co-exist with
214     existing system workqueue work items without an unacceptable impact;
215     for example, if the new work items perform blocking operations that
256   work queue has no items left.  Work items resubmitted from the workqueue
257   thread are accepted while a queue is draining, but work items from any other
262   delayable items, but if the queue is plugged and the deadline expires the
390 While the state of both regular and delayable work items can be determined
393 with work items after they've been submitted.  :c:func:`k_work_flush()`,
423 work thread to sleep will starve other work queue items, which may need to
456 Work items in isolation are self-locking, so you don't need to hold an
474   work is being cancelled or the queue is not accepting new items.  If this
521 rather than having to deal with cancellation and cleanup at points where items