From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@wdc.com>,
linux-nvme@lists.infradead.org,
Anton Eidelman <anton@lightbitslabs.com>
Subject: Re: [PATCH] nvme: drop scan_lock and always kick requeue list when removing namespaces
Date: Wed, 20 Oct 2021 19:25:00 +0200 [thread overview]
Message-ID: <20211020172500.GC4167@lst.de> (raw)
In-Reply-To: <e44c4a84-c678-ebb2-b267-c7557d824ac2@grimberg.me>
On Wed, Oct 20, 2021 at 06:33:48PM +0300, Sagi Grimberg wrote:
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
>
> Christoph, Keith, Hannes, Chaitanya,
> Do you see any issues with this?
No. I'll add it to nvme-5.16.
I'd love to kill the scan mutex entirely. For that we'll probably
need a per-tagset freeze in the block layer, which seems like a
pretty good idea to start with.
prev parent reply other threads:[~2021-10-20 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 5:59 [PATCH] nvme: drop scan_lock and always kick requeue list when removing namespaces Hannes Reinecke
2021-10-20 15:33 ` Sagi Grimberg
2021-10-20 15:57 ` Keith Busch
2021-10-20 17:25 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211020172500.GC4167@lst.de \
--to=hch@lst.de \
--cc=anton@lightbitslabs.com \
--cc=hare@suse.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox