| /linux/tools/workqueue/ |
| H A D | wq_dump.py | 96 workqueues = prog['workqueues'] variable
182 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
203 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
237 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
|
| H A D | wq_monitor.py | 54 workqueues = prog['workqueues'] variable
154 for wq in list_for_each_entry('struct workqueue_struct', workqueues.address_of_(), 'list'):
|
| /linux/Documentation/driver-api/crypto/iaa/ |
| H A D | iaa-crypto.rst | 93 With scalable mode, both shared and dedicated workqueues are available
116 With legacy mode, only dedicated workqueues are available for use.
126 With no IOMMU mode, only dedicated workqueues are available for use.
138 the user must first disable the IAA devices and workqueues, reset the
151 workqueues.
173 IAA workqueues need to be bound to the iaa_crypto driver.
195 driver, the available workqueues are 'rebalanced' such that work
215 When there are no IAA workqueues bound to the driver, the IAA crypto
310 The devices and workqueues are also enabled and therefore the driver
319 the enabled devices and workqueues must first be disabled. In order
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | workqueue.rst | 82 For threaded workqueues, special purpose threads, called [k]workers, execute
87 The cmwq design differentiates between the user-facing workqueues that
93 worker-pools to serve work items queued on unbound workqueues - the
96 BH workqueues use the same framework. However, as there can only be one
140 For unbound workqueues, the number of backing pools is dynamic.
176 BH workqueues can be considered a convenience interface to softirq. BH
177 workqueues are always per-CPU and all BH work items are executed in the
180 All BH workqueues must have 0 ``max_active`` and ``WQ_HIGHPRI`` is the
252 unbound workqueues.
395 worker on the same CPU. This makes unbound workqueues behave as per-cpu
[all …]
|
| /linux/fs/smb/smbdirect/ |
| H A D | internal.h | 27 } workqueues; member
|
| /linux/kernel/ |
| H A D | workqueue.c | 466 static LIST_HEAD(workqueues); /* PR: list of all workqueues */
5982 list_add_tail_rcu(&wq->list, &workqueues); in __alloc_workqueue()
6718 list_for_each_entry_rcu(wq, &workqueues, list) in show_all_workqueues()
6741 list_for_each_entry_rcu(wq, &workqueues, list) { in show_freezable_workqueues()
6973 list_for_each_entry(wq, &workqueues, list) { in workqueue_online_cpu()
7008 list_for_each_entry(wq, &workqueues, list) { in workqueue_offline_cpu()
7089 list_for_each_entry(wq, &workqueues, list) { in freeze_workqueues_begin()
7121 list_for_each_entry(wq, &workqueues, list) { in freeze_workqueues_busy()
7165 list_for_each_entry(wq, &workqueues, list) { in thaw_workqueues()
7185 list_for_each_entry(wq, &workqueues, list) { in workqueue_apply_unbound_cpumask()
[all …]
|
| /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?
|
| /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.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-crypt.rst | 117 Set dm-crypt workqueues and the writer thread to high priority. This
|
| /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
|
| /linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 82 the list macros (for example, include/linux/{,rcu}list.h), workqueues,
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 190 The location is clear when using workqueues or the kthread worker
|
| /linux/Documentation/RCU/ |
| H A D | checklist.rst | 553 If necessary, you can use something like workqueues to execute
|
| /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. |
|