From: Keith Busch <kbusch@kernel.org>
To: Amit Chaudhary <achaudhary@purestorage.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
mkhalfella@purestorage.com, randyj@purestorage.com,
jmeneghi@redhat.com, emilne@redhat.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] nvme-multipath: Skip nr_active increments in RETRY disposition
Date: Thu, 9 Oct 2025 09:10:34 -0600 [thread overview]
Message-ID: <aOfQatF6bqyE1OCF@kbusch-mbp> (raw)
In-Reply-To: <20250926190823.5031-1-achaudhary@purestorage.com>
On Fri, Sep 26, 2025 at 12:08:22PM -0700, Amit Chaudhary wrote:
> For queue-depth I/O policy, this patch fixes unbalanced I/Os across
> nvme multipaths.
Thanks, applied to nvme-6.18
prev parent reply other threads:[~2025-10-09 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 19:08 [PATCH v2 1/1] nvme-multipath: Skip nr_active increments in RETRY disposition Amit Chaudhary
2025-10-09 15:10 ` Keith Busch [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=aOfQatF6bqyE1OCF@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=achaudhary@purestorage.com \
--cc=axboe@kernel.dk \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=jmeneghi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mkhalfella@purestorage.com \
--cc=randyj@purestorage.com \
--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