All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>, Daniel Wagner <dwagner@suse.de>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org,
	sagi@grimberg.me, axboe@fb.com, gjoyce@linux.ibm.com
Subject: Re: [PATCH RFC 0/1] Add visibility for native NVMe miltipath using debugfs
Date: Thu, 25 Jul 2024 11:53:28 +0530	[thread overview]
Message-ID: <b24ac7d2-d5ea-4e5a-b59a-099ce4c48929@linux.ibm.com> (raw)
In-Reply-To: <20240724134152.GB12516@lst.de>



On 7/24/24 19:11, Christoph Hellwig wrote:
> On Tue, Jul 23, 2024 at 09:40:55AM +0200, Daniel Wagner wrote:
>> debugfs might always be available. IIRC when lockdown is enabled, debugfs
>> is not available or parts of it.
>>
>> I'd suggest going the full way and add expose the relevant information
>> via sysfs and extend libnvme and nvme-cli. But this just my take on this.
> 
> Yes, if we want to do this properly sysfs is the place to go, not
> debugfs.
> 
Alright, I will send out another patch with relevant changes for
sysfs and then latter in libnvme/nvme-cli.

Thanks,
--Nilay


  reply	other threads:[~2024-07-25  6:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22  9:31 [PATCH RFC 0/1] Add visibility for native NVMe miltipath using debugfs Nilay Shroff
2024-07-22  9:31 ` [PATCH RFC 1/1] nvme-multipath: Add debugfs entry for showing multipath info Nilay Shroff
2024-07-22 14:18 ` [PATCH RFC 0/1] Add visibility for native NVMe miltipath using debugfs Daniel Wagner
2024-07-23  5:18   ` Nilay Shroff
2024-07-23  7:40     ` Daniel Wagner
2024-07-24 13:41       ` Christoph Hellwig
2024-07-25  6:23         ` Nilay Shroff [this message]
2024-07-24 14:37 ` Keith Busch
2024-07-25  6:20   ` Nilay Shroff
2024-07-28 20:47 ` Sagi Grimberg
2024-07-29  4:50   ` 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=b24ac7d2-d5ea-4e5a-b59a-099ce4c48929@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@fb.com \
    --cc=dwagner@suse.de \
    --cc=gjoyce@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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 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.