Re: [PATCH 0/3] RDMA net namespace

yanjun.zhu
2022-10-27T03:17:28Z

October 27, 2022 11:10 AM, "Parav Pandit" <parav@nvidia.com> wrote:

>> From: yanjun.zhu@linux.dev <yanjun.zhu@linux.dev>
>> Sent: Wednesday, October 26, 2022 11:08 PM
>>
>> October 27, 2022 11:01 AM, "Parav Pandit" <parav@nvidia.com> wrote:
>>
>> From: Dust Li <dust.li@linux.alibaba.com>
>> Sent: Wednesday, October 26, 2022 10:31 PM
>>
>> 2. else we are in
>> exclusive mode. When the corresponding netdevice of the RoCE or iWarp
>> device is moved from one net namespace to another, we move the RDMA
>> device into that net namespace
>>
>> What do you think ?
>>
>> No. one device is not supposed to move other devices.
>> Every device is independent that should be moved by explicit command.
>>
>> Can you show us where we can find this rule "Every device is independent
>> that should be moved by explicit command."?
>>
>> Also changes like above breaks the existing orchestration, it no-go.
>>
>> In a RoCE device, ib device is related with the net device. When a net device
>> is moved to a new net namespace, if the ib device is not in the same net
>> device, how to make ib device work?
>
> RDMA device should also be moved to the same net namespace as that of netdev.

sure. I know the following commands.

In my commits, the process of moving IB devices to the same net namespace with net devices is automatically finished.

Is it OK?

Zhu Yanjun

>
> Steps should be,
>
> $ rdma system set netns exclusive
> $ ip netns add NSNAME
> $ ip link set [NETDEV] netns NSNAME
> $ rdma dev set [ RDMA_DEV ] netns NSNAME