From: John Meneghini <jmeneghi@redhat.com>
To: hare@suse.de
Cc: james.smart@broadcom.com, dick.kennedy@broadcom.com,
njavali@marvell.com, linux-scsi@vger.kernel.org, axboe@kernel.dk,
sagi@grimberg.me, hch@lst.de, kbusch@kernel.org,
linux-nvme@lists.infradead.org, Bryan Gurney <bgurney@redhat.com>
Subject: Re: [PATCH v8 8/8] nvme-multipath: queue-depth support for marginal paths
Date: Wed, 9 Jul 2025 18:03:31 -0400 [thread overview]
Message-ID: <66a05f2e-f3fd-4347-9c7f-f8fbb715890d@redhat.com> (raw)
In-Reply-To: <20250709212652.49471-1-bgurney@redhat.com>
Hannes, this patch fixes the queue-depth scheduler. Please take a look.
On 7/9/25 5:26 PM, Bryan Gurney wrote:
> From: John Meneghini <jmeneghi@redhat.com>
>
> Exclude marginal paths from queue-depth io policy. In the case where all
> paths are marginal and no optimized or non-optimized path is found, we
> fall back to __nvme_find_path which selects the best marginal path.
>
> Tested-by: Bryan Gurney <bgurney@redhat.com>
> Signed-off-by: John Meneghini <jmeneghi@redhat.com>
> ---
> drivers/nvme/host/multipath.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
> index 8d4e54bb4261..767583e8454b 100644
> --- a/drivers/nvme/host/multipath.c
> +++ b/drivers/nvme/host/multipath.c
> @@ -420,6 +420,9 @@ static struct nvme_ns *nvme_queue_depth_path(struct nvme_ns_head *head)
> if (nvme_path_is_disabled(ns))
> continue;
>
> + if (nvme_ctrl_is_marginal(ns->ctrl))
> + continue;
> +
> depth = atomic_read(&ns->ctrl->nr_active);
>
> switch (ns->ana_state) {
> @@ -443,7 +446,9 @@ static struct nvme_ns *nvme_queue_depth_path(struct nvme_ns_head *head)
> return best_opt;
> }
>
> - return best_opt ? best_opt : best_nonopt;
> + best_opt = (best_opt) ? best_opt : best_nonopt;
> +
> + return best_opt ? best_opt : __nvme_find_path(head, numa_node_id());
> }
>
> static inline bool nvme_path_is_optimized(struct nvme_ns *ns)
next prev parent reply other threads:[~2025-07-09 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 21:26 [PATCH v8 8/8] nvme-multipath: queue-depth support for marginal paths Bryan Gurney
2025-07-09 22:03 ` John Meneghini [this message]
2025-07-10 6:36 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2025-06-24 20:20 [PATCH v7 0/6] nvme-fc: FPIN link integrity handling Bryan Gurney
2025-07-11 2:59 ` [PATCH v8 8/8] nvme-multipath: queue-depth support for marginal paths Muneendra Kumar
2025-07-11 14:53 ` John Meneghini
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=66a05f2e-f3fd-4347-9c7f-f8fbb715890d@redhat.com \
--to=jmeneghi@redhat.com \
--cc=axboe@kernel.dk \
--cc=bgurney@redhat.com \
--cc=dick.kennedy@broadcom.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=njavali@marvell.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;
as well as URLs for NNTP newsgroup(s).