Commit 34cfb09c authored by Sagi Grimberg's avatar Sagi Grimberg Committed by Keith Busch
Browse files

nvmet: make nvmet_wq unbound



When deleting many controllers one-by-one, it takes a very
long time as these work elements may serialize as they are
scheduled on the executing cpu instead of spreading. In general
nvmet_wq can definitely be used for long standing work elements
so its better to make it unbound regardless.

Signed-off-by: default avatarSagi Grimberg <sagi.grimberg@vastdata.com>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
Signed-off-by: default avatarKeith Busch <kbusch@kernel.org>
parent 4b9a89be
Loading
Loading
Loading
Loading
+2 −1
Original line number Diff line number Diff line
@@ -1686,7 +1686,8 @@ static int __init nvmet_init(void)
	if (!buffered_io_wq)
		goto out_free_zbd_work_queue;

	nvmet_wq = alloc_workqueue("nvmet-wq", WQ_MEM_RECLAIM, 0);
	nvmet_wq = alloc_workqueue("nvmet-wq",
			WQ_MEM_RECLAIM | WQ_UNBOUND, 0);
	if (!nvmet_wq)
		goto out_free_buffered_work_queue;