From: Nilay Shroff <nilay@linux.ibm.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, kbusch@kernel.org,
gjoyce@ibm.com
Subject: Re: [PATCHv2 2/4] nvme: extend show-topology command to add support for multipath
Date: Wed, 3 Sep 2025 17:49:25 +0530 [thread overview]
Message-ID: <39141817-e3b6-4d74-8fe0-7cd567c656db@linux.ibm.com> (raw)
In-Reply-To: <9a878215-da92-408a-afb1-0e54e5770518@flourine.local>
On 9/3/25 12:54 PM, Daniel Wagner wrote:
> Hi Nilay,
>
> On Wed, Sep 03, 2025 at 09:52:13AM +0530, Nilay Shroff wrote:
>> Having said that, the “monitor” idea seems worth pursuing separately as a
>> longer-term feature. For users who want a live view today, they can already
>> run something like "watch -n1 nvme show-topology ..." to refresh the snapshot
>> every second. A built-in --monitor feature would be nicer and more efficient,
>> but I think that’s orthogonal and can be discussed separately. And I believe
>> "minitor" feature shall be useful as well for implementing nvme-top command
>> (as I recall we (me and Daniel) discussed it during LSFM-2025).
>
> Yes, I remember the discussion, me trying to convince you to implement it :)
Yeah I was convinced at the time :)
> I've created an issue on github, so we can track this feature:
>
> https://github.com/linux-nvme/nvme-cli/issues/2904
>
Okay good. I'll work on it once this patchset is merged.
Thanks,
--Nilay
next prev parent reply other threads:[~2025-09-03 13:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:56 [PATCHv2 0/4] nvme-cli: enhance the visibility of multipath using show-topology command Nilay Shroff
2025-08-12 12:56 ` [PATCHv2 1/4] nvme: support <device> option in " Nilay Shroff
2025-08-18 7:12 ` Hannes Reinecke
2025-08-19 4:43 ` Nilay Shroff
2025-08-19 6:11 ` Hannes Reinecke
2025-08-12 12:56 ` [PATCHv2 2/4] nvme: extend show-topology command to add support for multipath Nilay Shroff
2025-08-18 7:22 ` Hannes Reinecke
2025-08-19 4:49 ` Nilay Shroff
2025-08-19 6:15 ` Hannes Reinecke
2025-08-19 10:31 ` Nilay Shroff
2025-08-19 11:05 ` Hannes Reinecke
2025-08-19 11:30 ` Nilay Shroff
2025-08-20 8:17 ` Daniel Wagner
2025-08-20 8:30 ` Hannes Reinecke
2025-08-20 11:59 ` Nilay Shroff
2025-09-01 9:21 ` Nilay Shroff
2025-09-01 16:36 ` Daniel Wagner
2025-09-02 6:26 ` Hannes Reinecke
2025-09-03 4:22 ` Nilay Shroff
2025-09-03 7:24 ` Daniel Wagner
2025-09-03 12:19 ` Nilay Shroff [this message]
2025-08-12 12:56 ` [PATCHv2 3/4] nvme: add common APIs for printing tabular format output Nilay Shroff
2025-08-18 7:27 ` Hannes Reinecke
2025-08-19 8:56 ` Nilay Shroff
2025-08-20 8:23 ` Daniel Wagner
2025-08-12 12:56 ` [PATCHv2 4/4] nvme: add support for printing show-topology in tabular form Nilay Shroff
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=39141817-e3b6-4d74-8fe0-7cd567c656db@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=dwagner@suse.de \
--cc=gjoyce@ibm.com \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.