From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"ubraun@linux.vnet.ibm.com" <ubraun@linux.vnet.ibm.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: net/smc and the RDMA core
Date: Mon, 1 May 2017 17:29:38 +0000 [thread overview]
Message-ID: <1493659776.2665.7.camel@sandisk.com> (raw)
In-Reply-To: <20170501163311.GA22209@lst.de>
On Mon, 2017-05-01 at 18:33 +0200, Christoph Hellwig wrote:
> Hi Ursual, hi netdev reviewers,
>
> how did the smc protocol manage to get merged without any review
> on linux-rdma at all? As the results it seems it's very substandard
> in terms of RDMA API usage, e.g. it neither uses the proper CQ API
> nor the RDMA R/W API, and other will probably find additional issues
> as well.
Hello Dave and Ursula,
It seems very rude to me to have merged the SMC protocol driver without
having involved the linux-rdma community. Anyway, I have the following
questions for Dave and Ursula:
* Since the Linux kernel is standards based: where can we find the standard
that defines the SMC wire protocol? If this protocol has not been
standardized yet: in what file (other than *.[ch]) in the Linux kernel
tree has this protocol been documented?
* What are the differences between the SMC protocol, the SDP protocol and
the rsockets protocol? How do existing implementations for these protocols
compare to each other from a performance point of view? If no performance
comparison between these protocols is available, shouldn't the performance
of these protocols have been compared with each other before a review of
the SMC driver even started?
* What are the reasons why the SDP driver was never accepted upstream? Do
the arguments why SDP was not accepted upstream also apply to the SMC
driver (SDP = Sockets Direct Protocol)?
* Since SMC has to be selected by specifying AF_SMC, how are users expected
to specify whether AF_INET, AF_INET6 or yet another address family should
be used to set up a connection between SMC
endpoints?
* Is the SMC driver limited to RoCE? Are you aware that the rsockets library
supports multiple transport layers (RoCE, IB and iWARP)?
* Since functionality that is similar what the SMC driver provides already
exists in user space (rsockets), why has this functionality been
reimplemented as a kernel driver (SMC)?
Bart.
next prev parent reply other threads:[~2017-05-01 17:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 16:33 net/smc and the RDMA core Christoph Hellwig
2017-05-01 17:29 ` Bart Van Assche [this message]
[not found] ` <1493659776.2665.7.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-05-01 17:55 ` Parav Pandit
[not found] ` <HE1PR0502MB30048AFD086C4B0D535BFC52D1140-692Kmc8YnlL9PhveBwpv4cDSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-02 12:41 ` Ursula Braun
2017-05-02 15:37 ` Bart Van Assche
2017-05-02 12:34 ` Ursula Braun
[not found] ` <dce14470-06f4-8da3-6894-cd724eac3447-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-02 14:34 ` Doug Ledford
2017-05-01 21:04 ` Steve Wise
[not found] ` <20170501163311.GA22209-jcswGhMUV9g@public.gmane.org>
2017-05-02 12:25 ` Ursula Braun
[not found] ` <d9214af6-1c6f-9f95-fc00-3e4a316b4f81-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-02 18:39 ` Bart Van Assche
[not found] ` <1493750358.2552.13.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-05-03 14:40 ` Ursula Braun
2017-05-04 8:43 ` Sagi Grimberg
[not found] ` <1b79048f-4495-3840-e7a6-d4fa5a8dfb57-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-05-04 8:48 ` hch-jcswGhMUV9g
2017-05-04 13:08 ` Ursula Braun
[not found] ` <efa9bd6d-1df9-952a-7f32-c2ee6bffcae5-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-04 13:15 ` Leon Romanovsky
2017-05-04 15:31 ` Jason Gunthorpe
[not found] ` <20170504153155.GB854-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-05 17:06 ` Ursula Braun
2017-05-05 17:10 ` Jason Gunthorpe
2017-05-06 8:25 ` hch
[not found] ` <20170504084825.GA5399-jcswGhMUV9g@public.gmane.org>
2017-05-11 16:50 ` Ursula Braun
[not found] ` <869d9fb6-0d83-5f57-f8e4-5c1ee7477b94-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-11 16:56 ` hch-jcswGhMUV9g
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=1493659776.2665.7.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.vnet.ibm.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).