From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 1/1] RDMA over Fibre Channel
Date: Wed, 18 Apr 2018 06:18:31 -0700 [thread overview]
Message-ID: <20180418131831.GA23425@infradead.org> (raw)
In-Reply-To: <86f66430d0c577792b663226189d31a1@mail.gmail.com>
On Wed, Apr 18, 2018@05:17:25PM +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). However, there is a business case for the current soft
> RDMA implementation for FC, i.e. RDMA over FC-NVMe, as it provides
> existing Fibre channel customers a way to utilize existing FC network to
> transport RDMA workloads as well. While doing this we are making sure
> NVMe block traffic also can happen on the same FC network.
There might be a business case for you, but with my Linux NVMe
(co-)maintainer hat on I'll have to tell you that this abuse of the
Linux nvme code is a complete no-go.
And even if it wasn't we'd still require the protocol be ratified by the
NVMe technical working group first.
next prev parent reply other threads:[~2018-04-18 13:18 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 [this message]
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
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=20180418131831.GA23425@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.