[PATCH] nvmet: use a private workqueue instead of the system workqueue

Christoph Hellwig hch at lst.de
Tue Mar 22 04:15:20 PDT 2022


On Mon, Mar 21, 2022 at 01:57:27PM +0200, Sagi Grimberg wrote:
> Any attempt to flush kernel-global WQs has possibility of deadlock
> so we should simply stop using them, instead introduce nvmet_wq
> which is the generic nvmet workqueue for work elements that
> don't explicitly require a dedicated workqueue (by the mere fact
> that they are using the system_wq).
> 
> Changes were done using the following replaces:
> s/schedule_work(/queue_work(nvmet_wq, /g
> s/schedule_delayed_work(/queue_delayed_work(nvmet_wq, /g
> s/flush_scheduled_work()/flush_workqueue(nvmet_wq)/g

Should this have a Reported-by or Suggested-by for Tetsuo?



More information about the Linux-nvme mailing list