From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"parav@mellanox.com" <parav@mellanox.com>,
"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: Tue, 2 May 2017 15:37:07 +0000 [thread overview]
Message-ID: <1493739426.2552.1.camel@sandisk.com> (raw)
In-Reply-To: <dec979a3-a708-a814-ee99-777953fa4a4f@linux.vnet.ibm.com>
On Tue, 2017-05-02 at 14:41 +0200, Ursula Braun wrote:
> On 05/01/2017 07:55 PM, Parav Pandit wrote:
> > Hi Bart, Ursula, Dave,
> >
> > I am particularly concerned about SMC as address family.
> > It should not be treated as address family, but rather an additional
> > protocol similar for socket type SOCK_STREAM.
>
> We tried to avoid changes of the kernel TCP code. A new address family
> seemed to be a feasible way to achieve this.
Hello Ursula,
I agree with Parav that introducing a new address family for SMC was an
unfortunate choice. As one can see in e.g. the implementation of the SCTP
protocol no changes to the TCP implementation are needed to add support
for a new SOCK_STREAM protocol. I think the SCTP implementation uses
inet_register_protosw() to register itself dynamically.
Bart.
next prev parent reply other threads:[~2017-05-02 15:37 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
[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 [this message]
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=1493739426.2552.1.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=parav@mellanox.com \
--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).