Searched full:workqueue (Results 1 – 25 of 44) sorted by relevance
12
| /Documentation/core-api/ |
| D | workqueue.rst | 2 Workqueue title
14 is needed and the workqueue (wq) API is the most commonly used
20 queue is called workqueue and the thread is called worker.
22 While there are work items on the workqueue the worker executes the
24 there is no work item left on the workqueue the worker becomes idle.
28 Why Concurrency Managed Workqueue?
55 Concurrency Managed Workqueue (cmwq) is a reimplementation of wq with
58 * Maintain compatibility with the original workqueue API.
78 workqueue.
99 the BH execution context. A BH workqueue can be considered a convenience
[all …]
|
| D | tracepoint.rst | 51 Workqueue chapter
54 .. kernel-doc:: include/trace/events/workqueue.h
|
| D | index.rst | 20 workqueue
|
| /Documentation/translations/zh_CN/core-api/ |
| D | workqueue.rst | 4 :Original: Documentation/core-api/workqueue.rst
95 ``workqueue API`` 函数创建和排队工作项。他们可以通过在工作队列上
137 ``alloc_workqueue()`` 分配了一个wq。原来的 ``create_*workqueue()``
324 使用模块参数 ``workqueue.default_affinity_scope`` 指定
346 默认的亲和性作用域可以被模块参数 ``workqueue.default_affinity_scope``
350 如果设置了 ``WQ_SYSFS`` ，工作队列会在它的 ``/sys/devices/virtual/workqueue/WQ_NAME/``
537 使用 tools/workqueue/wq_dump.py（drgn脚本） 来检查未
540 $ tools/workqueue/wq_dump.py
592 Workqueue CPU -> pool
594 [ workqueue \ CPU 0 1 2 3 dfl]
[all …]
|
| D | index.rst | 30 workqueue
|
| /Documentation/fb/ |
| D | deferred_io.rst | 16 - schedule a workqueue task to be run after a delay
19 - the workqueue task comes in and mkcleans the pages on the list, then
70 from a workqueue.
|
| /Documentation/devicetree/bindings/media/ |
| D | mediatek,vcodec-subdev-decoder.yaml | 25 || lat || | core workqueue <parent>
38 There are two workqueues in parent device: lat workqueue and core workqueue. They are used
39 to lat and core hardware decoder. Lat workqueue need to get input bitstream and lat buffer,
41 done. Core workqueue need to get lat buffer and output buffer, then enable core to decode,
|
| /Documentation/driver-api/crypto/iaa/ |
| D | iaa-crypto.rst | 175 For instance, here's an example of configuring an IAA workqueue and
194 Whenever a new workqueue is bound to or unbound from the iaa_crypto
197 workqueue available. Current best practice is to configure and bind
198 at least one workqueue for each IAA device, but as long as there is at
199 least one workqueue configured and bound to any IAA device in the
205 binding of the first IAA workqueue to the iaa_crypto driver.
448 system to be configured properly as a kernel workqueue with a
449 workqueue driver_name of "crypto".
526 system to be configured properly as a kernel workqueue with a
527 workqueue driver_name of "crypto".
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 226 Execute workqueue requests
232 2. A given workqueue can be made visible in the sysfs filesystem
233 by passing the WQ_SYSFS to that workqueue's alloc_workqueue().
234 Such a workqueue can be confined to a given subset of the
235 CPUs using the ``/sys/devices/virtual/workqueue/*/cpumask`` sysfs
237 "ls /sys/devices/virtual/workqueue". That said, the workqueues
|
| D | xfs.rst | 504 Workqueue Concurrency
512 the generic workqueue implementation XFS uses for concurrency, and they are
519 /sys/bus/workqueue/devices/${task}!${device}
531 For example, the knobs for the quotacheck workqueue for /dev/nvme0n1 would be
532 found in /sys/bus/workqueue/devices/xfs_iwalk-1111!nvme0n1/.
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-dma-idxd | 62 the workqueue the descriptor was submitted to.
220 Description: The max transfer sized for this workqueue. Cannot exceed device
227 Description: The max batch size for this workqueue. Cannot exceed device
235 Description: Indicate whether ATS disable is turned on for the workqueue.
236 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue.
242 Description: Controls whether PRS disable is turned on for the workqueue.
244 workqueue. This option overrides block_on_fault attribute
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 113 The default is to use an unbound workqueue so that encryption work
130 Bypass dm-crypt internal workqueue and process read requests synchronously.
133 Bypass dm-crypt internal workqueue and process write requests synchronously.
|
| D | verity.rst | 146 verify data blocks in bottom half instead of workqueue. This option can
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-dsa | 18 filter_wq = "config1:0-31" - workqueue filter
|
| D | sysfs-class-devfreq | 125 This work timer is used by devfreq workqueue in order to
|
| /Documentation/driver-api/80211/ |
| D | mac80211.rst | 146 The mac80211 workqueue
150 :doc: mac80211 workqueue
|
| /Documentation/rust/ |
| D | testing.rst | 99 /// # use kernel::{spawn_work_item, workqueue};
100 /// spawn_work_item!(workqueue::system(), || pr_info!("x"))?;
|
| /Documentation/arch/x86/ |
| D | sva.rst | 155 * A single mmap() maps a single hardware workqueue as a "portal" and
156 each portal maps down to a single workqueue.
162 which case they still share one device hardware workqueue.
210 Communicating with the device via the shared workqueue is much simpler
|
| /Documentation/networking/ |
| D | nf_flowtable.rst | 198 There is a workqueue that adds the flows to the hardware. Note that a few
199 packets might still run over the flowtable software path until the workqueue has
|
| D | operstates.rst | 132 Whenever the driver CHANGES one of these flags, a workqueue event is
|
| /Documentation/RCU/ |
| D | lockdep.rst | 113 For example, the workqueue for_each_pwq() macro is intended to be used
|
| /Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 409 workqueues (see Documentation/core-api/workqueue.rst).
414 workqueue kthread does the actual grace-period processing. Because
415 workqueue kthreads do not accept POSIX signals, grace-period-wait
485 pre-workqueue stall-warning checks, but only during the mid-boot dead
502 workqueue.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 79 workqueue for event and asynchronous request completion, and also manages
538 All notifier callbacks are executed on a dedicated workqueue, the so-called
539 completion workqueue. After an event has been received via the callback
543 queue (running on the completion workqueue) will pick up the event and
|
| /Documentation/driver-api/usb/ |
| D | hotplug.rst | 64 hub workqueue [hub_wq], or else as part of root hub initialization
|
| /Documentation/networking/device_drivers/ethernet/google/ |
| D | gve.rst | 110 the workqueue to check the register and acks the irq.
|
12