Searched refs:WQ_SYSFS (Results 1 – 11 of 11) sorted by relevance
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 233 by passing the WQ_SYSFS to that workqueue's alloc_workqueue().
236 files. The set of WQ_SYSFS workqueues can be displayed using
239 sprinkling WQ_SYSFS across all the workqueues. The reason for
240 caution is that it is easy to add WQ_SYSFS, but because sysfs is
|
| /Linux-v5.4/drivers/infiniband/hw/hfi1/ |
| D | opfn.c | 308 WQ_SYSFS | WQ_HIGHPRI | WQ_CPU_INTENSIVE | in opfn_init()
|
| D | init.c | 808 WQ_SYSFS | WQ_HIGHPRI | WQ_CPU_INTENSIVE | in create_workqueues()
823 WQ_SYSFS | WQ_MEM_RECLAIM | WQ_UNBOUND, in create_workqueues()
|
| /Linux-v5.4/include/linux/ |
| D | workqueue.h | 314 WQ_SYSFS = 1 << 6, /* visible in sysfs, see wq_sysfs_register() */ enumerator
|
| /Linux-v5.4/mm/ |
| D | backing-dev.c | 243 WQ_SYSFS, 0); in default_bdi_init()
|
| /Linux-v5.4/drivers/infiniband/core/ |
| D | device.c | 2698 WQ_HIGHPRI | WQ_MEM_RECLAIM | WQ_SYSFS, 0); in ib_core_init()
2707 WQ_SYSFS, WQ_UNBOUND_MAX_ACTIVE); in ib_core_init()
|
| /Linux-v5.4/drivers/nvme/host/ |
| D | core.c | 4236 WQ_UNBOUND | WQ_MEM_RECLAIM | WQ_SYSFS, 0); in nvme_core_init()
4241 WQ_UNBOUND | WQ_MEM_RECLAIM | WQ_SYSFS, 0); in nvme_core_init()
4246 WQ_UNBOUND | WQ_MEM_RECLAIM | WQ_SYSFS, 0); in nvme_core_init()
|
| /Linux-v5.4/block/ |
| D | blk-cgroup.c | 1838 WQ_UNBOUND | WQ_SYSFS, 0); in blkcg_init()
|
| /Linux-v5.4/drivers/ntb/test/ |
| D | ntb_perf.c | 1496 perf_wq = alloc_workqueue("perf_wq", WQ_UNBOUND | WQ_SYSFS, 0); in perf_init()
|
| /Linux-v5.4/kernel/ |
| D | workqueue.c | 4283 if ((wq->flags & WQ_SYSFS) && workqueue_sysfs_register(wq)) in alloc_workqueue()
|
| /Linux-v5.4/drivers/md/ |
| D | raid5.c | 8491 WQ_UNBOUND|WQ_MEM_RECLAIM|WQ_CPU_INTENSIVE|WQ_SYSFS, 0); in raid5_init()
|
