Skip to content

Commit 43fa47c

Browse files
author
Mike Snitzer
committed
dm verity: remove WQ_CPU_INTENSIVE flag since using WQ_UNBOUND
The documentation [1] says that WQ_CPU_INTENSIVE is "meaningless" for unbound wq. So remove WQ_CPU_INTENSIVE from the verify_wq allocation. 1. https://www.kernel.org/doc/html/latest/core-api/workqueue.html#flags Suggested-by: Maksym Planeta <[email protected]> Signed-off-by: Mike Snitzer <[email protected]>
1 parent e9307e3 commit 43fa47c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

drivers/md/dm-verity-target.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1388,7 +1388,7 @@ static int verity_ctr(struct dm_target *ti, unsigned argc, char **argv)
13881388
}
13891389

13901390
/* WQ_UNBOUND greatly improves performance when running on ramdisk */
1391-
v->verify_wq = alloc_workqueue("kverityd", WQ_CPU_INTENSIVE | WQ_MEM_RECLAIM | WQ_UNBOUND, num_online_cpus());
1391+
v->verify_wq = alloc_workqueue("kverityd", WQ_MEM_RECLAIM | WQ_UNBOUND, num_online_cpus());
13921392
if (!v->verify_wq) {
13931393
ti->error = "Cannot allocate workqueue";
13941394
r = -ENOMEM;

0 commit comments

Comments
 (0)