Commit 3ec8db61 authored by Ryo Takakura's avatar Ryo Takakura Committed by Yu Kuai
Browse files

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: default avatarRyo Takakura <ryotkkr98@gmail.com>
Acked-by: default avatarTejun Heo <tj@kernel.org>
Link: https://lore.kernel.org/linux-raid/20250601013702.64640-1-ryotkkr98@gmail.com


Signed-off-by: default avatarYu Kuai <yukuai3@huawei.com>
parent 790abe4d

drivers/md/raid5.c

+1 −1
Original line number Diff line number Diff line
@@ -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;