From: Bart.VanAssche@wdc.com (Bart Van Assche)
Subject: [PATCH 1/1] RDMA over Fibre Channel
Date: Wed, 18 Apr 2018 13:39:11 +0000 [thread overview]
Message-ID: <5fd3da7b3182eeb1b7416c9192202adecc7383e3.camel@wdc.com> (raw)
In-Reply-To: <86f66430d0c577792b663226189d31a1@mail.gmail.com>
On Wed, 2018-04-18@17:17 +0530, Muneendra Kumar M wrote:
> Although we concur with the idea of RDMA directly over Fibre channel, the
> actual implementation addressing the above reasons requires
> standardization and coordination with FC HBA vendors and other SAN
> ecosystem players. This effort is ongoing within our organization (Brocade
> at Broadcom).
What makes you think that a new standardization effort would have to be
launched to make RDMA over FC possible? RDMA over FC was standardized a long
time ago and is called "FC-VI". Why aren't you using that standard? A quote
from the FC-VI document:
Table 1 ? VI and FC-VI functions
................................
VI function FC-VI equivalent
VI Message Exchange
Request/Response primitives Sequence
VI Connect/Disconnect request Unsolicited control IU
VI Connect response Solicited control IU
VI Send Data Solicited data IU
VI Send Response Command status IU
VI RDMA Write Request Solicited data IU
VI RDMA Write Response Command status IU
VI RDMA Read Request Unsolicited command IU
VI RDMA Read Response Solicited data IU
See also ANSI/INCITS 357:2002, "Fibre Channel Virtual Interface Architecture
Mapping Protocol (FC-VI)", NCITS Project 1332-D, July 2000.
Bart.
prev parent reply other threads:[~2018-04-18 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180418094240.26371-1-muneendra.kumar@broadcom.com>
2018-04-18 10:22 ` [PATCH 1/1] RDMA over Fibre Channel Christoph Hellwig
2018-04-18 11:47 ` Muneendra Kumar M
2018-04-18 13:18 ` Christoph Hellwig
2018-04-18 16:53 ` Anand Nataraja Sundaram
2018-04-19 9:39 ` Christoph Hellwig
2018-04-23 11:48 ` Anand Nataraja Sundaram
2018-04-18 13:39 ` Bart Van Assche [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=5fd3da7b3182eeb1b7416c9192202adecc7383e3.camel@wdc.com \
--to=bart.vanassche@wdc.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.