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]

Message-ID: <CAGgvQNRjSVcOfQB3bhXTdPoa04Hs7jc1+hXvL99EqDjbaaOw=A@mail.gmail.com>
Date:	Tue, 19 May 2015 22:09:14 +0530
From:	Parav Pandit <parav.pandit@...gotech.com>
To:	Haggai Eran <haggaie@...lanox.com>
Cc:	Yann Droneaud <ydroneaud@...eya.com>,
	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 Tue, May 19, 2015 at 8:24 PM, Haggai Eran <haggaie@...lanox.com> wrote:
> 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.
>

This has come up during our first round of patch set for RoCEv2.
However due to last set of changes in this patch set, we decided to
move in for later submission.

Current high design approach to support this is:

A callback function registered to IP stack for IP address
assignment/removal. (it could be done possibly done for GID entry
update, instead of IP)
For each such namespace, for device supporting RoCEv2, one UDP socket
with RoCEv2 UDP port would be created and destroyed.



> Regards,
> Haggai
>
> [1] http://www.spinics.net/lists/linux-rdma/msg25156.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.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