From: james.p.freyensee@intel.com (Freyensee, James P)
Subject: targetcli and nvmetcli
Date: Fri, 6 Jan 2017 20:34:56 +0000 [thread overview]
Message-ID: <1483734894.5538.14.camel@intel.com> (raw)
In-Reply-To: <cab11273-41c3-9af5-9263-e4d251b2c927@redhat.com>
On Fri, 2017-01-06@11:05 -0800, Andy Grover wrote:
> Hi James and Christoph,
>
> Have you considered integrating nvmetcli with targetcli?
>
> I see there being reasons why it was developed as a standalone, but I'm?
> not sure how many of these still apply.
>
> Especially given their shared source history, combining them at the cli?
> level, or even the lib level, would be straightforward, and could give?
> users a unified tool for managing both types of targets.
>
> What do you think?
I donno, in my opinion, it seems from support/maintenance to philosophy
difference it would be confusing and difficult to combine the two. ?NVMe is a
new storage protocol with its own terminology (ex namespaces vs LUNS), defined
in its own standard, written by its own standard body that reserves the right
to not necessarily follow what iSCSI does (though there are a few borrowed
concepts like IQNs), and is supported by its own Linux email list.
Christoph has done design work on both the NVMe Target and LIO so he could give
a more intelligent technical answer than me.
Jay
>
> Thanks -- Regards -- Andy
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2017-01-06 20:34 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 [this message]
2017-01-08 9:58 ` Christoph Hellwig
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=1483734894.5538.14.camel@intel.com \
--to=james.p.freyensee@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.