[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGgvQNQk7ZeK72SPE4zjNQkD783G+tTXsM0jpnD9_4tNaLxFbg@mail.gmail.com>
Date: Wed, 20 May 2015 00:12:09 +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" <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 v4 for-next 00/12] Add network namespace support in the RDMA-CM
On Tue, May 19, 2015 at 11:31 PM, Haggai Eran <haggaie@...lanox.com> wrote:
> On Tuesday, May 19, 2015 7:39 PM, Parav Pandit <parav.pandit@...gotech.com> wrote:
>> 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.
>
> This needs to be done to take ownership of the RoCEv2 UDP port of course, but there is more to RoCE namespace support then that. You will need to de-multiplex rdma_cm_id requests from a shared ib_cm_id similarly to what is done in the InfiniBand patch-set here. Using the new RoCE GID cache should make it relatively easy. In addition, in order to support link-layer address resolution in the verbs layer as it is done today, we may need to add namespace support to the modify QP verb and the create AH verb.
>
Yes. We talked sometime back with Liran and Matan on same topic.
> Haggai
--
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
Powered by blists - more mailing lists