From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v4 5/7] nvme-fabrics: Add host support for FC transport
Date: Sat, 05 Nov 2016 11:07:24 -0700 [thread overview]
Message-ID: <1478369244.17308.4.camel@linux.intel.com> (raw)
In-Reply-To: <581cf3c5.i79zcsb/mXCT8ar6%james.smart@broadcom.com>
On Fri, 2016-11-04@13:47 -0700, 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>
>
> ---
> v4 mods:
> - added HAS_DMA to Kconfig
> - Changed to support Christophs nvme_request update
> - addressed return code in __nvme_fc_abort_op()
> - fixed possible op->rq NULL reference in nvme_fc_start_fcp_op()
> - FC-NVME v1.11: process transferred length in ersp iu and rsp iu
> mandates
> - Add comments on teardown flow
> - fix bad cqe reference in fcpio_done
Looks good, nice work James,
Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
prev parent reply other threads:[~2016-11-05 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 20:47 [PATCH v4 5/7] nvme-fabrics: Add host support for FC transport James Smart
2016-11-05 18:07 ` J Freyensee [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=1478369244.17308.4.camel@linux.intel.com \
--to=james_p_freyensee@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).