[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <87ddcac4c4e017a42e20dbbfcb8343468a0efc12.1641857023.git.mirq-linux@rere.qmqm.pl>
Date: Tue, 11 Jan 2022 00:25:06 +0100
From: Michał Mirosław <mirq-linux@...e.qmqm.pl>
To: Alasdair Kergon <agk@...hat.com>, Mike Snitzer <snitzer@...hat.com>
Cc: dm-devel@...hat.com, linux-kernel@...r.kernel.org
Subject: [PATCH 1/2] dm integrity: use alloc_ordered_workqueue() for
dm-integrity-wait
Make the requirement for ordering of dm-integrity-wait work
explicit. No behaviour change because of commit 5c0338c68706
("workqueue: restore WQ_UNBOUND/max_active==1 to be ordered").
Signed-off-by: Michał Mirosław <mirq-linux@...e.qmqm.pl>
---
drivers/md/dm-integrity.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/md/dm-integrity.c b/drivers/md/dm-integrity.c
index 7af242de3202..6dc9aebf8487 100644
--- a/drivers/md/dm-integrity.c
+++ b/drivers/md/dm-integrity.c
@@ -4212,7 +4212,7 @@ static int dm_integrity_ctr(struct dm_target *ti, unsigned argc, char **argv)
* If this workqueue were percpu, it would cause bio reordering
* and reduced performance.
*/
- ic->wait_wq = alloc_workqueue("dm-integrity-wait", WQ_MEM_RECLAIM | WQ_UNBOUND, 1);
+ ic->wait_wq = alloc_ordered_workqueue("dm-integrity-wait", WQ_MEM_RECLAIM);
if (!ic->wait_wq) {
ti->error = "Cannot allocate workqueue";
r = -ENOMEM;
--
2.30.2
Powered by blists - more mailing lists