nvmet: make nvmet_wq unbound
authorSagi Grimberg <sagi.grimberg@vastdata.com>
Tue, 7 May 2024 06:54:10 +0000 (09:54 +0300)
committerKeith Busch <kbusch@kernel.org>
Tue, 7 May 2024 15:07:05 +0000 (08:07 -0700)
commit34cfb09cdc75457a671279165a88a0739a170f07
tree27c66ee00586139fa3c264949eabf645d0396695
parent4b9a89be214235acbff003232baba123c868a25c
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: Sagi Grimberg <sagi.grimberg@vastdata.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
drivers/nvme/target/core.c