diff options
| author | Ryo Takakura <[email protected]> | 2025-06-01 01:37:02 +0000 |
|---|---|---|
| committer | Yu Kuai <[email protected]> | 2025-07-12 09:52:11 +0000 |
| commit | 3ec8db61e7852b0d0637483c8fd249533d701bff (patch) | |
| tree | 78c57aa7fd22393c903d2341e5cfc9c74ac65e1d | |
| parent | md: remove/add redundancy group only in level change (diff) | |
| download | kernel-3ec8db61e7852b0d0637483c8fd249533d701bff.tar.gz kernel-3ec8db61e7852b0d0637483c8fd249533d701bff.zip | |
md/raid5: unset WQ_CPU_INTENSIVE for raid5 unbound workqueue
When specified with WQ_CPU_INTENSIVE, the workqueue doesn't
participate in concurrency management. This behaviour is already
accounted for WQ_UNBOUND workqueues given that they are assigned
to their own worker threads.
Unset WQ_CPU_INTENSIVE as the use of flag has no effect when
used with WQ_UNBOUND.
Signed-off-by: Ryo Takakura <[email protected]>
Acked-by: Tejun Heo <[email protected]>
Link: https://lore.kernel.org/linux-raid/[email protected]
Signed-off-by: Yu Kuai <[email protected]>
| -rw-r--r-- | drivers/md/raid5.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index ca5b0e8ba707..7ec61ee7b218 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -9040,7 +9040,7 @@ static int __init raid5_init(void) int ret; raid5_wq = alloc_workqueue("raid5wq", - WQ_UNBOUND|WQ_MEM_RECLAIM|WQ_CPU_INTENSIVE|WQ_SYSFS, 0); + WQ_UNBOUND|WQ_MEM_RECLAIM|WQ_SYSFS, 0); if (!raid5_wq) return -ENOMEM; |