From: Christoph Hellwig <hch@lst.de>
To: guzebing <guzebing1612@gmail.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Guzebing <guzebing@bytedance.com>
Subject: Re: [RFC PATCH 0/1] nvme-pci: detect I/O queue depth changes after reset
Date: Wed, 27 May 2026 15:19:51 +0200 [thread overview]
Message-ID: <20260527131951.GA11071@lst.de> (raw)
In-Reply-To: <20260527075320.3178600-1-guzebing1612@gmail.com>
On Wed, May 27, 2026 at 03:53:19PM +0800, guzebing wrote:
> This RFC instead takes the smaller approach of detecting the reset-time
> CAP.MQES change and making it visible. If the live I/O queue depth
> shrinks, reset recovery is failed before recreating I/O queues. If it
> grows, the driver warns and continues with the existing queue resources.
Unlike the other version this at least sounds doable without creating
a complete mess. So if we can live with this version that'd make me
much happier.
next prev parent reply other threads:[~2026-05-27 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 7:53 [RFC PATCH 0/1] nvme-pci: detect I/O queue depth changes after reset guzebing
2026-05-27 7:53 ` [RFC PATCH 1/1] " guzebing
2026-05-27 13:19 ` Christoph Hellwig [this message]
2026-05-28 1:38 ` [RFC PATCH 0/1] " guzebing
2026-05-28 3:03 ` Keith Busch
2026-05-28 8:44 ` Christoph Hellwig
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=20260527131951.GA11071@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=guzebing1612@gmail.com \
--cc=guzebing@bytedance.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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