public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: John Meneghini <jmeneghi@redhat.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"emilne@redhat.com" <emilne@redhat.com>,
	"jrani@purestorage.com" <jrani@purestorage.com>,
	"randyj@purestorage.com" <randyj@purestorage.com>,
	"hare@kernel.org" <hare@kernel.org>
Subject: Re: [PATCH v8 2/2] nvme-multipath: implement "queue-depth" iopolicy
Date: Wed, 26 Jun 2024 08:19:46 +0000	[thread overview]
Message-ID: <fb69b60d-b2ad-4a3f-87c7-a3779184edd9@nvidia.com> (raw)
In-Reply-To: <20240625122605.857462-3-jmeneghi@redhat.com>

On 6/25/24 05:26, John Meneghini wrote:
> From: Thomas Song<tsong@purestorage.com>
>
> The round-robin path selector is inefficient in cases where there is a
> difference in latency between paths.  In the presence of one or more
> high latency paths the round-robin selector continues to use the high
> latency path equally. This results in a bias towards the highest latency
> path and can cause a significant decrease in overall performance as IOs
> pile on the highest latency path. This problem is acute with NVMe-oF
> controllers.
>
> The queue-depth path selector sends I/O down the path with the lowest
> number of requests in its request queue. Paths with lower latency will
> clear requests more quickly and have less requests queued compared to
> higher latency paths. The goal of this path selector is to make more use
> of lower latency paths which will bring down overall IO latency and
> increase throughput and performance.
>
> Signed-off-by: Thomas Song<tsong@purestorage.com>
> [emilne: patch developed by Thomas Song @ Pure Storage, fixed whitespace
>        and compilation warnings, updated MODULE_PARM description, and
>        fixed potential issue with ->current_path[] being used]
> Co-developed-by: Ewan D. Milne<emilne@redhat.com>
> Signed-off-by: Ewan D. Milne<emilne@redhat.com>
> [jmeneghi: various changes and improvements, addressed review comments]
> Co-developed-by: John Meneghini<jmeneghi@redhat.com>
> Signed-off-by: John Meneghini<jmeneghi@redhat.com>
> Link:https://lore.kernel.org/linux-nvme/20240509202929.831680-1-jmeneghi@redhat.com/
> Tested-by: Marco Patalano<mpatalan@redhat.com>
> Reviewed-by: Randy Jennings<randyj@purestorage.com>
> Tested-by: Jyoti Rani<jrani@purestorage.com>
> Tested-by: John Meneghini<jmeneghi@redhat.com>
> Reviewed-by: Hannes Reinecke<hare@suse.de>

thanks for sharing github link, those scripts are in-general helpful ...

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck




  parent reply	other threads:[~2024-06-26  8:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 12:26 [PATCH v8 0/2] nvme: queue-depth multipath iopolicy John Meneghini
2024-06-25 12:26 ` [PATCH v8 1/2] nvme-multipath: prepare for "queue-depth" iopolicy John Meneghini
2024-06-26  5:05   ` Christoph Hellwig
2024-06-26  8:02   ` Chaitanya Kulkarni
2024-06-26  8:24   ` Sagi Grimberg
2024-06-25 12:26 ` [PATCH v8 2/2] nvme-multipath: implement " John Meneghini
2024-06-26  5:06   ` Christoph Hellwig
2024-06-26  8:19   ` Chaitanya Kulkarni [this message]
2024-06-26  8:24   ` Sagi Grimberg
2024-06-25 16:37 ` [PATCH v8 0/2] nvme: queue-depth multipath iopolicy Keith Busch
2024-06-26 16:54   ` Keith Busch
2024-06-26 17:26     ` Randy Jennings

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=fb69b60d-b2ad-4a3f-87c7-a3779184edd9@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=emilne@redhat.com \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=jrani@purestorage.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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