Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "wagi@kernel.org" <wagi@kernel.org>,
	"martinus.gpy@gmail.com" <martinus.gpy@gmail.com>
Subject: Re: [PATCH 1/2] nvme: avoid printing iopolicy in list-subsys output
Date: Mon, 12 Jan 2026 23:47:33 +0000	[thread overview]
Message-ID: <74d585b0-8665-4865-b1b4-867c4fc02bc7@nvidia.com> (raw)
In-Reply-To: <20260112111731.1631091-2-nilay@linux.ibm.com>

On 1/12/26 03:16, Nilay Shroff wrote:
> 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>
> ---

Looks good.

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

-ck


  reply	other threads:[~2026-01-12 23:47 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 ` [PATCH 1/2] nvme: avoid printing iopolicy in list-subsys output Nilay Shroff
2026-01-12 23:47   ` Chaitanya Kulkarni [this message]
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=74d585b0-8665-4865-b1b4-867c4fc02bc7@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martinus.gpy@gmail.com \
    --cc=nilay@linux.ibm.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