From: linda.knippers@hp.com (Linda Knippers)
Subject: [PATCH v2] nvme-user: Minor enhancement and fixes
Date: Tue, 02 Dec 2014 14:10:09 -0500 [thread overview]
Message-ID: <547E0E91.60706@hp.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1412011529540.4225@localhost.lm.intel.com>
On 12/01/2014 10:45 AM, Keith Busch wrote:
> On Fri, 28 Nov 2014, Swati C wrote:
>> Addressing comments from -
>> [PATCH] nvme-user: Minor enhancement and fixes
>> (http://lists.infradead.org/pipermail/linux-nvme/2014-November/001214.html)
>>
>>
>> Minor enhancements to nvme_format_ns.c
>> - Make Metadata Settings a user settable value.
>> - Support for Secure Erase Settings.
>>
>> Signed-off-by: Swati C <s.chawdhary at samsung.com>
>
> Thanks, applied.
>
> On a side note, some people asked if I could take the example programs
> here and turn it into something more useful with just one program to
> run all nvme instead of a bunch of stand-alone programs. I took a stab
> at it:
>
> http://git.infradead.org/users/kbusch/linux-nvme-cli.git
>
> It's still a work in progress, but just linking here in case others
> have ideas or find it useful too.
Thanks, I think something like this will be very helpful.
I noticed that FreeBSD already has an nvmecontrol command.
https://www.freebsd.org/cgi/man.cgi?query=nvmecontrol&sektion=8&apropos=0&manpath=FreeBSD+10.1-RELEASE
I haven't tried it or looked to see what the functional differences
are between nvmecontrol and your nvme, if any. Have you?
Thanks,
-- ljk
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2014-12-02 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 13:50 [PATCH v2] nvme-user: Minor enhancement and fixes Swati C
2014-12-01 15:45 ` Keith Busch
2014-12-02 19:10 ` Linda Knippers [this message]
2014-12-02 19:32 ` Keith Busch
2014-12-05 16:40 ` Zakaria Abushima (zabushima)
2014-12-05 16:48 ` James R. Bergsten
2014-12-05 16:58 ` Keith Busch
2014-12-08 14:36 ` Zakaria Abushima (zabushima)
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=547E0E91.60706@hp.com \
--to=linda.knippers@hp.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.