From: hch@lst.de (Christoph Hellwig)
Subject: targetcli and nvmetcli
Date: Sun, 8 Jan 2017 10:58:50 +0100 [thread overview]
Message-ID: <20170108095850.GA25936@lst.de> (raw)
In-Reply-To: <cab11273-41c3-9af5-9263-e4d251b2c927@redhat.com>
On Fri, Jan 06, 2017@11:05:01AM -0800, Andy Grover wrote:
> Hi James and Christoph,
>
> Have you considered integrating nvmetcli with targetcli?
We looked into all the options earlier and decided against it.
The NVMe object are a lot more standardized than those for the SCSI
transports, and both the kernel nvme target condigfs code, and thus
nvmetcli take advantage of that to provide a more coherent user interface.
prev parent reply other threads:[~2017-01-08 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 19:05 targetcli and nvmetcli Andy Grover
2017-01-06 20:34 ` Freyensee, James P
2017-01-08 9:58 ` Christoph Hellwig [this message]
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=20170108095850.GA25936@lst.de \
--to=hch@lst.de \
/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.