RE: [PATCH 0/3] RDMA net namespace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: yanjun.zhu@xxxxxxxxx <yanjun.zhu@xxxxxxxxx>
> Sent: Wednesday, October 26, 2022 11:08 PM
> 
> October 27, 2022 11:01 AM, "Parav Pandit" <parav@xxxxxxxxxx> wrote:
> 
> >> From: Dust Li <dust.li@xxxxxxxxxxxxxxxxx>
> >> 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.

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







[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux