| /openbmc/linux/tools/workqueue/ |
| H A D | wq_dump.py | 79 workqueues = prog['workqueues'] variable
156 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
|
| H A D | wq_monitor.py | 61 workqueues = prog['workqueues'] variable
161 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | kernel-per-CPU-kthreads.rst | 149 2. Convert all drivers that you must use from tasklets to workqueues.
236 files. The set of WQ_SYSFS workqueues can be displayed using
237 "ls /sys/devices/virtual/workqueue". That said, the workqueues
239 sprinkling WQ_SYSFS across all the workqueues. The reason for
248 use of each CPU's workqueues to run its cache_reap()
|
| H A D | xfs.rst | 507 XFS uses kernel workqueues to parallelize metadata update processes. This
516 The control knobs for a filesystem's workqueues are organized by task at hand
534 The interesting knobs for XFS workqueues are as follows:
|
| H A D | kernel-parameters.txt | 2326 A residual 1Hz tick is offloaded to workqueues, which you
7118 to use in unbound workqueues.
7121 unbound workqueues.
7142 candidates for using WQ_UNBOUND workqueues instead.
7145 Per-cpu workqueues are generally preferred because
7147 locality; unfortunately, per-cpu workqueues tend to
7148 be more power hungry than unbound workqueues.
7150 Enabling this makes the per-cpu workqueues which
7161 workqueues. Can be one of "cpu", "smt", "cache",
7168 workqueues with the "default" affinity scope will be
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | workqueue.rst | 85 The cmwq design differentiates between the user-facing workqueues that
91 worker-pools to serve work items queued on unbound workqueues - the
132 For unbound workqueues, the number of backing pools is dynamic.
227 unbound workqueues.
369 worker on the same CPU. This makes unbound workqueues behave as per-cpu
370 workqueues without concurrency management.
424 necessitating explicit configurations when workqueues are heavily used.
575 the workqueues using ``apply_workqueue_attrs()`` and/or enable
596 configuration, worker pools and how workqueues map to the pools: ::
|
| /openbmc/linux/kernel/power/ |
| H A D | Kconfig | 314 Per-cpu workqueues are generally preferred because they show
316 per-cpu workqueues tend to be more power hungry than unbound
317 workqueues.
320 per-cpu workqueues which were observed to contribute
|
| /openbmc/linux/kernel/ |
| H A D | workqueue.c | 4746 list_add_tail_rcu(&wq->list, &workqueues); in alloc_workqueue()
5314 list_for_each_entry_rcu(wq, &workqueues, list) in show_all_workqueues()
5567 list_for_each_entry(wq, &workqueues, list) { in workqueue_online_cpu()
5595 list_for_each_entry(wq, &workqueues, list) { in workqueue_offline_cpu()
5698 list_for_each_entry(wq, &workqueues, list) { in freeze_workqueues_begin()
5731 list_for_each_entry(wq, &workqueues, list) { in freeze_workqueues_busy()
5776 list_for_each_entry(wq, &workqueues, list) { in thaw_workqueues()
5797 list_for_each_entry(wq, &workqueues, list) { in workqueue_apply_unbound_cpumask()
5891 list_for_each_entry(wq, &workqueues, list) { in wq_affn_dfl_set()
6694 list_for_each_entry(wq, &workqueues, list) { in workqueue_init()
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | sva.rst | 153 * Devices have a limited number (~10's to 1000's) of hardware workqueues.
154 The device driver manages allocating hardware workqueues.
184 * How are shared workqueues different?
|
| /openbmc/linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 409 workqueues (see Documentation/core-api/workqueue.rst).
462 The use of workqueues has the advantage that the expedited grace-period
464 corresponding disadvantage that workqueues cannot be used until they are
472 the use of workqueues. However, the requesting task is only required to
475 workqueues are used.
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | mediatek,vcodec-subdev-decoder.yaml | 38 There are two workqueues in parent device: lat workqueue and core workqueue. They are used
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/ |
| H A D | dpaa.rst | 163 range from 0 (lowest) to 3 (highest). These are mapped to HW workqueues with
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcubarrier.rst | 79 If latency is of the essence, workqueues could be used to run these
|
| H A D | checklist.rst | 530 If necessary, you can use something like workqueues to execute
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-dma-idxd | 201 for dispatching work from multiple workqueues in the same group.
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 82 the list macros (for example, include/linux/{,rcu}list.h), workqueues,
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 190 The location is clear when using workqueues or the kthread worker
|
| /openbmc/linux/Documentation/spi/ |
| H A D | spi-summary.rst | 615 execution contexts like IRQ handlers, tasklets, or workqueues (such
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 1294 threads or (in the Linux kernel) workqueues.
1798 | on workqueues, but during the dead zone the requesting task itself |
1801 | dead zone ends, expedited grace periods go back to using workqueues, |
1915 | you can always use workqueues to invoke them concurrently. |
|
| /openbmc/linux/init/ |
| H A D | Kconfig | 687 any source of "noise" such as unbound workqueues, timers, kthreads...
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.debug | 1196 Say Y here to enable stall detection on workqueues. If a
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-online-fsck-design.rst | 4892 Thanks to Dave Chinner, bounded workqueues in userspace enable ``xfs_scrub`` to
|