netdev - Re: [PATCH v3 for-next 00/13] Add network namespace support in the RDMA-CM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150513171823.GB20343@obsidianresearch.com>
Date:	Wed, 13 May 2015 11:18:23 -0600
From:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:	"Hefty, Sean" <sean.hefty@...el.com>
Cc:	Haggai Eran <haggaie@...lanox.com>,
	Doug Ledford <dledford@...hat.com>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Liran Liss <liranl@...lanox.com>,
	Guy Shapiro <guysh@...lanox.com>,
	Shachar Raindel <raindel@...lanox.com>,
	Yotam Kenneth <yotamke@...lanox.com>
Subject: Re: [PATCH v3 for-next 00/13] Add network namespace support in the
 RDMA-CM

On Wed, May 13, 2015 at 04:45:59PM +0000, Hefty, Sean wrote:
> > > How does network namespace support work with iWarp?
> > 
> > We did not implement network namespace support for iWarp. Only for
> > InfiniBand. The iWarp code continues to use &init_net whenever a network
> > namespace is needed, as it does today.
> 
> We need a solution that supports both.  It's odd for the RDMA CM to
> support a feature only for some devices, when the solution should be
> general.

Yes, it is not optimal, but given that every protocol uses a
completely different scheme to interact with netdev, I'm not sure
there is another option but to do them piecemeal?

I'm happy to see this patch much smaller and without the vestigial
half-roce support that the prior version included.

This should be a good starting point for someone to do iWarp, it is
pretty simple since there is no UD component. roce will be much
harder, I think.

Should we inhibit the RDMA uapi on non-init namespaces? At least
that way iWarp/etc won't work at all, instead of leaking through the
container.

Jason
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html