netdev - Re: [PATCH v4 for-next 00/12] 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 19 May 2015 17:54:54 +0300
From:	Haggai Eran <haggaie@...lanox.com>
To:	Yann Droneaud <ydroneaud@...eya.com>
CC:	Doug Ledford <dledford@...hat.com>, <linux-rdma@...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 v4 for-next 00/12] Add network namespace support in the
 RDMA-CM

On 19/05/2015 17:30, Yann Droneaud wrote:
>Le dimanche 17 mai 2015 à 08:50 +0300, Haggai Eran a écrit :
>> Full support for RoCE will be introduced in a later stage.
>>
> How does this play with iWarp: as iWarp HCA are aware of IP addresses /
> UDP/TCP ports, AFAIK, are those tied to namespace with this patchset or
> will it be possible to use the iWarp HCA to access to address/port
> resources tied to a different namespace ?

At the moment the patchset doesn't add iWarp namespace support, as I
wrote in the discussion about v3 [1]. I suspect that the current iWarp
code lets users listen in one namespace and receive requests belonging
to the init namespace, or break the namespaces in similar ways. The
patchset doesn't attempt to fix this for iWarp or RoCE, only for InfiniBand.

Regards,
Haggai

[1] http://www.spinics.net/lists/linux-rdma/msg25156.html

--
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