From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH v5 5/7] nvme-fabrics: Add host support for FC transport
Date: Mon, 7 Nov 2016 09:45:53 +0100 [thread overview]
Message-ID: <20161107084553.tzbnmnbdxpftvcxb@linux-x5ow.site> (raw)
In-Reply-To: <58201df4.eHDpXvb36YEr/bgi%jsmart2021@gmail.com>
On Sun, Nov 06, 2016@10:23:48PM -0800, James Smart wrote:
>
> Add nvme-fabrics host support for FC transport
>
> Implements the FC-NVME T11 definition of how nvme fabric capsules are
> performed on an FC fabric. Utilizes a lower-layer API to FC host adapters
> to send/receive FC-4 LS operations and FCP operations that comprise NVME
> over FC operation.
>
> The T11 definitions for FC-4 Link Services are implemented which create
> NVMeOF connections. Implements the hooks with blk-mq to then submit admin
> and io requests to the different connections.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
Looks good,
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
prev parent reply other threads:[~2016-11-07 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 6:23 [PATCH v5 5/7] nvme-fabrics: Add host support for FC transport James Smart
2016-11-07 6:56 ` Hannes Reinecke
2016-11-07 8:45 ` Johannes Thumshirn [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=20161107084553.tzbnmnbdxpftvcxb@linux-x5ow.site \
--to=jthumshirn@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox