From: Ryo Takakura Date: Sun, 1 Jun 2025 01:37:02 +0000 (+0900) Subject: md/raid5: unset WQ_CPU_INTENSIVE for raid5 unbound workqueue X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3ec8db61e7852b0d0637483c8fd249533d701bff;p=thirdparty%2Fkernel%2Flinux.git 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 Acked-by: Tejun Heo Link: https://lore.kernel.org/linux-raid/20250601013702.64640-1-ryotkkr98@gmail.com Signed-off-by: Yu Kuai --- diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index ca5b0e8ba707f..7ec61ee7b2181 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;