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 <[email protected]>

Author: Mike Snitzer

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) {