October 11, 2022 11:08 PM, "Yanjun Zhu" <yanjun.zhu@xxxxxxxxx> wrote: > 在 2022/10/11 18:12, Leon Romanovsky 写道: > >> On Mon, Oct 10, 2022 at 08:25:45PM -0400, Zhu Yanjun wrote: >>> From: Zhu Yanjun <yanjun.zhu@xxxxxxxxx> >>> >>> This is not an official commit. In rdma net namespace, the rdma device >>> is separate from the net device. For example, a rdma device A is in net >>> namespace A1 while the related net device B is in net namespace B1. >>> >>> I am curious how to make perftest and rping tests on the above >>> scenario. The ip address of net device B is in net namespace B1 >>> while the rdma device is in net namespace A1. >> >> Use "exclusive" mode, "shared" is legacy interface for backward >> compatibility. > > Got it. Thanks. > >>> From my perspective, the rdma device and related net device should >>> be in the same net namespace. When a net device is moved from one net >>> namespace to another net namespace, the rdma device should be in the >>> same net namespace with the net device. >>> >>> In this commit, when all the ib devices are parsed in exclusive mode, >>> if the ib devices and related net devices are not in the same net >>> namespace, the link information will not be reported to user space. >>> >>> This commit is a RFC. >> >> Please don't send patches as reply-to. > > OK. I will send another commit to fix this problem very soon. Hi, Leon Per discussion, to the non-legacy ib device, when the net devices are moved from one net namespace to another net namespace, the related ib devices are also moved to the new net namespace. To the legacy ib device, shared/exclusive mode still work with them. Based on the above, 2 patches are implemented. I will send them out very soon. Thanks and Regards, Zhu Yanjun > > Zhu Yanjun > >> Thanks
