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 <ryotkkr98@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Link: https://lore.kernel.org/linux-raid/20250601013702.64640-1-ryotkkr98@gmail.com
Signed-off-by: Yu Kuai <yukuai3@huawei.com>

diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index ca5b0e8ba707f02d712dddff4f2029bcd81c4155..7ec61ee7b218172774fafae73789a9b407b64b8d 100644 (file)
--- 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;