diff options
| author | Mike Snitzer <snitzer@kernel.org> | 2024-04-12 17:58:05 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@kernel.org> | 2024-04-23 18:20:16 +0300 |
| commit | 83637d9017b22a5e11ada9f44ba776beb807222b (patch) | |
| tree | 3ae0247a9e6fdcd0ae84348253b2961e0e09dbdb | |
| parent | 1c0e720228ad1c63bb487cdcead2558353b5a067 (diff) | |
| download | linux-83637d9017b22a5e11ada9f44ba776beb807222b.tar.xz | |
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 <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 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) { |