From: Tony Asleson <tasleson@redhat.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Keith Busch <kbusch@kernel.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Tomas Bzatek <tbzatek@redhat.com>
Subject: Re: libnvme questions
Date: Fri, 12 Mar 2021 09:35:14 -0600 [thread overview]
Message-ID: <7e866844-4848-3ef6-cba2-c704a8db74b9@redhat.com> (raw)
In-Reply-To: <BYAPR04MB49654A2227C054ACC903E2ED86909@BYAPR04MB4965.namprd04.prod.outlook.com>
On 3/10/21 10:43 PM, Chaitanya Kulkarni wrote:
> Keith,
>
> On 3/10/21 12:56, Keith Busch wrote:
>>> 3. Any plans on adding functionality for NVMe management interfaces to
>>> the library, e.g. NVMe Enclosures?
>> Will be happen to incorporate any features that are in-spec.
>>
>
> Adding MI support is good idea ? I think it will bloat the basic
> functionality.
>
> Can we consider adding MI plug-in for it ?
>
IMHO having standards based functionality only in the cli as a plugin
diminishes the value of the library. If a developer is required to fork
& exec the cli for some functionality, just do it for all.
If the size of libnvme is a concern, MI could be built into a separate
library from the same source tree that leverages the base libnvme
library, to allow selective install & use.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-03-12 15:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:14 libnvme questions Tony Asleson
2021-03-08 7:48 ` Chaitanya Kulkarni
2021-03-10 20:48 ` Keith Busch
2021-03-11 4:43 ` Chaitanya Kulkarni
2021-03-12 15:35 ` Tony Asleson [this message]
2021-03-12 16:18 ` Keith Busch
2021-04-07 12:38 ` Padmakar Kalghatgi
2021-04-07 23:16 ` Chaitanya Kulkarni
2021-04-08 7:48 ` Padmakar Kalghatgi
2021-04-09 3:58 ` Chaitanya Kulkarni
2021-04-09 5:48 ` Klaus Jensen
2021-04-12 11:48 ` Padmakar Kalghatgi
2021-04-07 23:19 ` Chaitanya Kulkarni
2021-04-08 7:50 ` Padmakar Kalghatgi
2021-04-07 23:37 ` Keith Busch
2021-04-08 7:51 ` Padmakar Kalghatgi
2021-04-08 16:46 ` Keith Busch
2021-04-12 8:56 ` Padmakar Kalghatgi
2021-04-08 12:09 ` Christoph Hellwig
2021-03-31 14:15 ` Hannes Reinecke
2021-03-31 14:54 ` Keith Busch
2021-03-31 15:29 ` Hannes Reinecke
2021-04-07 21:34 ` Keith Busch
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=7e866844-4848-3ef6-cba2-c704a8db74b9@redhat.com \
--to=tasleson@redhat.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=tbzatek@redhat.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