From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v3 1/3] nvme_fc: create fc class and transport device
Date: Wed, 20 Sep 2017 10:50:18 -0700 [thread overview]
Message-ID: <20170920175018.GA8962@infradead.org> (raw)
In-Reply-To: <20170920103041.idkzk5kerewgv5yk@linux-x5ow.site>
On Wed, Sep 20, 2017@12:30:41PM +0200, Johannes Thumshirn wrote:
> the problem with libfc currently is it is made for fcoe, despite being named
> libfc.
Well, that's my point - we should be able to use more bits in a common
FC layer. I don't really care about the exact name.
> The other hand it is hard-wired to FCP so bringing NVMe into it is a
> bit challanging, BTDT.
FC-NVMe layers on top of FCP.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
James Smart <jsmart2021@gmail.com>,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 1/3] nvme_fc: create fc class and transport device
Date: Wed, 20 Sep 2017 10:50:18 -0700 [thread overview]
Message-ID: <20170920175018.GA8962@infradead.org> (raw)
In-Reply-To: <20170920103041.idkzk5kerewgv5yk@linux-x5ow.site>
On Wed, Sep 20, 2017 at 12:30:41PM +0200, Johannes Thumshirn wrote:
> the problem with libfc currently is it is made for fcoe, despite being named
> libfc.
Well, that's my point - we should be able to use more bits in a common
FC layer. I don't really care about the exact name.
> The other hand it is hard-wired to FCP so bringing NVMe into it is a
> bit challanging, BTDT.
FC-NVMe layers on top of FCP.
next prev parent reply other threads:[~2017-09-20 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 17:38 [PATCH v3 0/3] nvme_fc: add uevent to allow dynamic connects James Smart
2017-09-14 17:38 ` [PATCH v3 1/3] nvme_fc: create fc class and transport device James Smart
2017-09-18 16:13 ` Christoph Hellwig
2017-09-18 16:13 ` Christoph Hellwig
2017-09-20 10:30 ` Johannes Thumshirn
2017-09-20 10:30 ` Johannes Thumshirn
2017-09-20 17:50 ` Christoph Hellwig [this message]
2017-09-20 17:50 ` Christoph Hellwig
2017-09-21 5:16 ` Johannes Thumshirn
2017-09-21 5:16 ` Johannes Thumshirn
2017-09-14 17:38 ` [PATCH v3 2/3] nvme_fc: add uevent for auto-connect James Smart
2017-09-18 16:14 ` Christoph Hellwig
2017-09-19 14:53 ` James Smart
2017-09-20 17:50 ` Christoph Hellwig
2017-09-14 17:38 ` [PATCH v3 3/3] nvme_fc: Avoid duplicate associations between same port pairs James Smart
2017-09-18 16:12 ` Christoph Hellwig
2017-09-18 16:28 ` James Smart
2017-09-18 23:17 ` Christoph Hellwig
2017-09-19 0:07 ` James Smart
2017-09-20 11:09 ` Sagi Grimberg
2017-10-04 7:48 ` [PATCH v3 0/3] nvme_fc: add uevent to allow dynamic connects 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=20170920175018.GA8962@infradead.org \
--to=hch@infradead.org \
/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.