From: Daniel Wagner <dwagner@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: 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: nvme-cli spdk plugin
Date: Wed, 17 Apr 2024 10:33:17 +0200 [thread overview]
Message-ID: <xulnfwru3jfl2nooq27yym7nx3cdpxqslzqz5nvwnkymncapnt@pzascju2tmvf> (raw)
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?
Obviously, it would be nice if we could discover the spdk devices via
sysfs.
Thoughts?
https://github.com/linux-nvme/nvme-cli/pull/2295
next reply other threads:[~2024-04-17 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:33 Daniel Wagner [this message]
2024-04-17 9:44 ` nvme-cli spdk plugin Sagi Grimberg
2024-04-17 10:17 ` Brzezinka, Sebastian
2024-04-17 11:47 ` Daniel Wagner
2024-04-17 14:26 ` Christoph Hellwig
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=xulnfwru3jfl2nooq27yym7nx3cdpxqslzqz5nvwnkymncapnt@pzascju2tmvf \
--to=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).