From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: wagi@kernel.org, martinus.gpy@gmail.com
Subject: [PATCH 0/2] nvme-cli: limit printing iopolicy in subsystem header
Date: Mon, 12 Jan 2026 16:45:59 +0530 [thread overview]
Message-ID: <20260112111731.1631091-1-nilay@linux.ibm.com> (raw)
Hi,
The nvme-cli currently prints the iopolicy value in the subsystem header
for both the show-topology and list-subsys commands. This behavior was
introduced by commit d0b4c6cf0006 (“nvme: extend show-topology command
to add support for multipath”).
Printing the iopolicy value in the output of the show-topology command is
intentional and useful. The command also displays additional columns such
as Nodes or queue-depth, depending on the configured I/O policy. Including
the iopolicy in the header makes it easier to correlate the output with the
active policy and understand the resulting I/O path behavior.
However, the iopolicy value is not particularly relevant for the list-subsys
command. It currently appears there for non-verbose output because both
show-topology and list-subsys commands share a common helper function that
prints the subsystem header. As a result, the iopolicy field unintentionally
leaked into the list-subsys output.
In addition, while the iopolicy field is shown in the regular text output
of show-topology, it was missing from the JSON output format when show-topology
is executed in non-verbose mode. This patchset addresses both of these issues
and consists of two patches:
First patch avoids printing the iopolicy field in the list-subsys output
unless the command is invoked with the verbose flag.
Second patch adds the iopolicy field to the JSON output of the show-topology
command.
Thanks!
Nilay Shroff (2):
nvme: avoid printing iopolicy in list-subsys output
nvme: add iopolicy field in JSON output
nvme-print-json.c | 4 ++--
nvme-print-stdout.c | 14 ++++++++------
2 files changed, 10 insertions(+), 8 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-12 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 11:15 Nilay Shroff [this message]
2026-01-12 11:16 ` [PATCH 1/2] nvme: avoid printing iopolicy in list-subsys output Nilay Shroff
2026-01-12 23:47 ` Chaitanya Kulkarni
2026-01-13 7:29 ` Martin George
2026-01-12 11:16 ` [PATCH 2/2] nvme: add iopolicy field in JSON output Nilay Shroff
2026-01-12 23:47 ` Chaitanya Kulkarni
2026-01-13 7:31 ` Martin George
2026-01-14 9:37 ` [PATCH 0/2] nvme-cli: limit printing iopolicy in subsystem header Daniel Wagner
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=20260112111731.1631091-1-nilay@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=linux-nvme@lists.infradead.org \
--cc=martinus.gpy@gmail.com \
--cc=wagi@kernel.org \
/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