Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: hare@suse.de, kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
	dwagner@suse.de, kanie@linux.alibaba.com, jmeneghi@redhat.com,
	randyj@purestorage.com, martin.petersen@oracle.com,
	john.g.garry@oracle.com, gjoyce@linux.ibm.com
Subject: [PATCHv6 8/8] nvme-multipath: add documentation for latency I/O policy
Date: Wed, 20 May 2026 23:51:04 +0530	[thread overview]
Message-ID: <20260520182112.863076-9-nilay@linux.ibm.com> (raw)
In-Reply-To: <20260520182112.863076-1-nilay@linux.ibm.com>

Update the nvme-multipath documentation to describe the latency I/O
policy, its behavior, and when it is suitable for use.

Suggested-by: Guixin Liu <kanie@linux.alibaba.com>
Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
---
 Documentation/admin-guide/nvme-multipath.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/Documentation/admin-guide/nvme-multipath.rst b/Documentation/admin-guide/nvme-multipath.rst
index 97ca1ccef459..41a8054638ff 100644
--- a/Documentation/admin-guide/nvme-multipath.rst
+++ b/Documentation/admin-guide/nvme-multipath.rst
@@ -70,3 +70,22 @@ When to use the queue-depth policy:
   1. High load with small I/Os: Effectively balances load across paths when
      the load is high, and I/O operations consist of small, relatively
      fixed-sized requests.
+
+Latency
+--------
+
+The latency policy manages I/O requests based on path latency. It periodically
+calculates a weight for each path and distributes I/O accordingly. Paths with
+higher latency receive lower weights, resulting in fewer I/O requests being sent
+to them, while paths with lower latency handle a proportionally larger share of
+the I/O load.
+
+When to use the latency policy
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1. Homogeneous Path Performance: Utilizes all available paths efficiently when
+   their performance characteristics (e.g., latency, bandwidth) are similar.
+
+2. Heterogeneous Path Performance: Dynamically distributes I/O based on per-path
+   performance characteristics. Paths with lower latency receive a higher share
+   of I/O compared to those with higher latency.
-- 
2.53.0



      parent reply	other threads:[~2026-05-20 18:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 18:20 [PATCHv6 0/8] nvme-multipath: introduce latency I/O policy Nilay Shroff
2026-05-20 18:20 ` [PATCHv6 1/8] block: expose blk_stat_{enable,disable}_accounting() to drivers Nilay Shroff
2026-05-21 12:06   ` John Garry
2026-05-22  6:18     ` Nilay Shroff
2026-05-22 12:10       ` Christoph Hellwig
2026-05-20 18:20 ` [PATCHv6 2/8] nvme-multipath: pass I/O type to nvme_find_path() Nilay Shroff
2026-05-27  7:16   ` Hannes Reinecke
2026-05-20 18:20 ` [PATCHv6 3/8] nvme-multipath: add support for latency I/O policy Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 4/8] nvme: add generic debugfs support Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 5/8] nvme-multipath: add debugfs attribute latency_ewma_shift Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 6/8] nvme-multipath: add debugfs attribute latency_batch_timeout Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 7/8] nvme-multipath: add debugfs attribute latency_stat Nilay Shroff
2026-05-20 18:21 ` Nilay Shroff [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=20260520182112.863076-9-nilay@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=dwagner@suse.de \
    --cc=gjoyce@linux.ibm.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=john.g.garry@oracle.com \
    --cc=kanie@linux.alibaba.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.petersen@oracle.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