From: Guixin Liu <kanie@linux.alibaba.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>,
Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH v2 3/3] nvme: document the service-time iopolicy sysfs attributes
Date: Mon, 19 Oct 2026 15:56:05 +0800 [thread overview]
Message-ID: <20261019075607.808947-4-kanie@linux.alibaba.com> (raw)
In-Reply-To: <20261019075607.808947-1-kanie@linux.alibaba.com>
The service-time iopolicy adds two sysfs attributes to the NVMe path
namespace devices: in_flight_bytes, reporting the bytes currently in
flight on the path's controller, and relative_throughput, the
per-path throughput weight used by the service-time estimation.
Document both in the stable sysfs ABI, including the 0-100 value
range, the default of 1, and the standby semantics of a
relative_throughput of 0.
Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
---
Documentation/ABI/stable/sysfs-nvme | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/Documentation/ABI/stable/sysfs-nvme b/Documentation/ABI/stable/sysfs-nvme
index a2f5d0710db40..adaf292c8c67b 100644
--- a/Documentation/ABI/stable/sysfs-nvme
+++ b/Documentation/ABI/stable/sysfs-nvme
@@ -326,6 +326,28 @@ Description:
currently selected path. Returns empty if iopolicy is not
"numa". Requires CONFIG_NVME_MULTIPATH.
+What: /sys/block/nvmeXcYnZ/in_flight_bytes
+What: /sys/block/nvmeXcYnZ/relative_throughput
+Date: October 2026
+KernelVersion: 7.5
+Contact: Guixin Liu <kanie@linux.alibaba.com>
+Description:
+ in_flight_bytes: Shows the number of bytes currently in
+ flight on this path's controller. Returns empty if
+ iopolicy is not "service-time".
+ Requires CONFIG_NVME_MULTIPATH.
+
+ relative_throughput: Shows or sets the relative
+ throughput weight of this path, which the "service-time"
+ iopolicy uses to estimate the path service time as
+ in_flight_bytes / relative_throughput. The value is an
+ integer in the range 0-100 and defaults to 1; assign
+ higher values to faster paths. A path with a value of 0
+ is only selected when no path with a positive value is
+ available. Reading returns empty if iopolicy is not
+ "service-time"; writing is accepted regardless of the
+ active policy. Requires CONFIG_NVME_MULTIPATH.
+
What: /sys/block/nvmeXnY/delayed_removal_secs
Date: May 2025
KernelVersion: 6.16
--
2.43.7
next prev parent reply other threads:[~2026-10-19 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 7:56 [PATCH v2 0/3] nvme: introduce the service-time iopolicy Guixin Liu
2026-10-19 7:56 ` [PATCH v2 1/3] nvme-multipath: implement " Guixin Liu
2026-10-19 8:14 ` sashiko-bot
2026-10-19 7:56 ` [PATCH v2 2/3] nvme-multipath: document " Guixin Liu
2026-10-19 7:56 ` Guixin Liu [this message]
2026-10-19 8:13 ` [PATCH v2 3/3] nvme: document the service-time iopolicy sysfs attributes sashiko-bot
2026-10-19 11:13 ` Guixin Liu
2026-10-19 12:13 ` Martin George
2026-10-19 12:43 ` Laurence Oberman
2026-10-19 13:21 ` Guixin Liu
2026-10-19 14:46 ` Martin George
2026-10-19 14:51 ` Laurence Oberman
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=20261019075607.808947-4-kanie@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.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