From 83637d9017b22a5e11ada9f44ba776beb807222b Mon Sep 17 00:00:00 2001 From: Mike Snitzer Date: Fri, 12 Apr 2024 10:58:05 -0400 Subject: dm-crypt: don't set WQ_CPU_INTENSIVE for WQ_UNBOUND crypt_queue Fix crypt_queue's use of WQ_UNBOUND to _not_ use WQ_CPU_INTENSIVE because it is meaningless with WQ_UNBOUND. Signed-off-by: Mike Snitzer --- drivers/md/dm-crypt.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'drivers/md') diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c index f43a2c0b3d77..1b7a97cc3779 100644 --- a/drivers/md/dm-crypt.c +++ b/drivers/md/dm-crypt.c @@ -3431,8 +3431,12 @@ static int crypt_ctr(struct dm_target *ti, unsigned int argc, char **argv) common_wq_flags | WQ_CPU_INTENSIVE, 1, devname, wq_id); } else { + /* + * While crypt_queue is certainly CPU intensive, the use of + * WQ_CPU_INTENSIVE is meaningless with WQ_UNBOUND. + */ cc->crypt_queue = alloc_workqueue("kcryptd-%s-%d", - common_wq_flags | WQ_CPU_INTENSIVE | WQ_UNBOUND, + common_wq_flags | WQ_UNBOUND, num_online_cpus(), devname, wq_id); } if (!cc->crypt_queue) { -- cgit v1.2.3