From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Tomasz Zawadzki <tomasz.zawadzki@intel.com>,
Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
Hannes Reinecke <hare@suse.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvme-cli spdk plugin
Date: Wed, 17 Apr 2024 16:26:10 +0200 [thread overview]
Message-ID: <20240417142610.GA31809@lst.de> (raw)
In-Reply-To: <xulnfwru3jfl2nooq27yym7nx3cdpxqslzqz5nvwnkymncapnt@pzascju2tmvf>
On Wed, Apr 17, 2024 at 10:33:17AM +0200, Daniel Wagner wrote:
> There is a PR [1] pending, adding a spdk plugin for nvme-cli. The
> problem this new plugin tries to solve is, that with the recent change
> to use sysfs only for discovering the nvme subystem, nvme-cli
> lost support for spdk.
>
> My question is, should we have a special plugin for 'list' and
> 'list-subsystem' or should we try to get this somehow integrated into
> the existing code? So that 'list' just works?
І don't think nvme-cli should deal with anything that is not driven
by the kernel nvme driver.
next prev parent reply other threads:[~2024-04-17 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:33 nvme-cli spdk plugin Daniel Wagner
2024-04-17 9:44 ` Sagi Grimberg
2024-04-17 10:17 ` Brzezinka, Sebastian
2024-04-17 11:47 ` Daniel Wagner
2024-04-17 14:26 ` Christoph Hellwig [this message]
2024-04-17 14:31 ` Jens Axboe
2024-04-17 14:39 ` Jim
2024-04-17 14:57 ` Jens Axboe
2024-04-17 15:13 ` Jim
2024-04-18 6:25 ` Hannes Reinecke
2024-04-18 14:44 ` Keith Busch
2024-04-18 16:17 ` Zawadzki, Tomasz
2024-04-18 9:22 ` Sagi Grimberg
2024-04-18 12:04 ` 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=20240417142610.GA31809@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sebastian.brzezinka@intel.com \
--cc=tomasz.zawadzki@intel.com \
/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.