From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: wagi@kernel.org, martinus.gpy@gmail.com
Subject: [PATCH 1/2] nvme: avoid printing iopolicy in list-subsys output
Date: Mon, 12 Jan 2026 16:46:00 +0530 [thread overview]
Message-ID: <20260112111731.1631091-2-nilay@linux.ibm.com> (raw)
In-Reply-To: <20260112111731.1631091-1-nilay@linux.ibm.com>
Since commit d0b4c6cf0006 (“nvme: extend show-topology command to add
support for multipath”), the subsystem header printed by both show-
topology and list-subsys includes the iopolicy field regardless of
whether the verbose flag is specified.
For show-topology, this behavior is intentional and useful. The command
now prints additional columns such as Nodes or queue-depth depending on
the configured I/O policy, and displaying the iopolicy value makes it
easier to correlate the output with the active policy configured for
the subsystem.
However, the same iopolicy field is also printed in the list-subsys
output, where it is not always relevant. This happens because both
commands share the common helper stdout_subsys_config() to print the
subsystem header.
This change fixes the inconsistency by always printing the iopolicy
field for show-topology, while suppressing it for list-subsys unless
the command is invoked with the verbose flag.
Fixes: d0b4c6cf0006 ("nvme: extend show-topology command to add support for multipath")
Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
---
nvme-print-stdout.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/nvme-print-stdout.c b/nvme-print-stdout.c
index 7995052a3..9a4fe80d9 100644
--- a/nvme-print-stdout.c
+++ b/nvme-print-stdout.c
@@ -1135,7 +1135,7 @@ static void stdout_subsystem_ctrls(nvme_subsystem_t s)
}
}
-static void stdout_subsys_config(nvme_subsystem_t s)
+static void stdout_subsys_config(nvme_subsystem_t s, bool show_iopolicy)
{
int len = strlen(nvme_subsystem_get_name(s));
@@ -1143,8 +1143,9 @@ static void stdout_subsys_config(nvme_subsystem_t s)
nvme_subsystem_get_nqn(s));
printf("%*s hostnqn=%s\n", len, " ",
nvme_host_get_hostnqn(nvme_subsystem_get_host(s)));
- printf("%*s iopolicy=%s\n", len, " ",
- nvme_subsystem_get_iopolicy(s));
+ if (show_iopolicy)
+ printf("%*s iopolicy=%s\n", len, " ",
+ nvme_subsystem_get_iopolicy(s));
if (stdout_print_ops.flags & VERBOSE) {
printf("%*s model=%s\n", len, " ",
@@ -1179,7 +1180,8 @@ static void stdout_subsystem(struct nvme_global_ctx *ctx, bool show_ana)
printf("\n");
first = false;
- stdout_subsys_config(s);
+ stdout_subsys_config(s,
+ stdout_print_ops.flags & VERBOSE);
printf("\\\n");
if (!show_ana || !stdout_subsystem_multipath(s))
@@ -6057,7 +6059,7 @@ static void stdout_topology_tabular(struct nvme_global_ctx *ctx)
printf("\n");
first = false;
- stdout_subsys_config(s);
+ stdout_subsys_config(s, true);
printf("\n");
if (nvme_is_multipath(s))
@@ -6090,7 +6092,7 @@ static void stdout_simple_topology(struct nvme_global_ctx *ctx,
printf("\n");
first = false;
- stdout_subsys_config(s);
+ stdout_subsys_config(s, true);
printf("\\\n");
if (nvme_is_multipath(s))
--
2.52.0
next prev parent reply other threads:[~2026-01-12 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 11:15 [PATCH 0/2] nvme-cli: limit printing iopolicy in subsystem header Nilay Shroff
2026-01-12 11:16 ` Nilay Shroff [this message]
2026-01-12 23:47 ` [PATCH 1/2] nvme: avoid printing iopolicy in list-subsys output 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-2-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