diff options
| author | Mike Snitzer <snitzer@kernel.org> | 2024-04-12 10:58:05 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@kernel.org> | 2024-04-12 12:49:47 -0400 |
| commit | 4b00f92cd36f53d8bbb47bae0b94b9d1630c501d (patch) | |
| tree | fbc4d1406d4547d566c7666718af5285cc08254e | |
| parent | 03ec77c1f6971b9af14ca0f074827500bdd2c903 (diff) | |
| download | linux-dm-6.10.tar.gz | |
dm-crypt: don't set WQ_CPU_INTENSIVE for WQ_UNBOUND crypt_queuedm-6.10
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 <snitzer@kernel.org>
| -rw-r--r-- | drivers/md/dm-crypt.c | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c index f43a2c0b3d77c0..1b7a97cc377943 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) { |