From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>, Zhu Yanjun <yanjun.zhu@intel.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 0/3] RDMA net namespace
Date: Sun, 23 Oct 2022 21:42:00 +0800 [thread overview]
Message-ID: <ac6228a7-52a6-3b80-6b22-c4444b67d360@linux.dev> (raw)
In-Reply-To: <Y1U7w+6emBqrQnkI@unreal>
在 2022/10/23 21:04, Leon Romanovsky 写道:
> On Sun, Oct 23, 2022 at 06:04:47PM -0400, Zhu Yanjun wrote:
>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>>
>> There are shared and exclusive modes in RDMA net namespace. After
>> discussion with Leon, the above modes are compatible with legacy IB
>> device.
>>
>> To the RoCE and iWARP devices, the ib devices should be in the same net
>> namespace with the related net devices regardless of in shared or
>> exclusive mode.
>>
>> In the first commit, when the net devices are moved to a new net
>> namespace, the related ib devices are also moved to the same net
>> namespace.
> I think that rdma_dev_net_ops are supposed to handle this.
Yes. rdma_dev_net_ops can move ib devices from one net to another net.
But these functions are called by a netlink command "rdma dev...".
In my commit, to RoCE devices, ib devices and net devices should be in
the same net.
That is, when the net devices are moved to another net, the ib devices
are moved
to the same net automically instead of running a netlink command to move
ib devices.
To legacy ib devices, this netlink command is needed. To RoCE devices,
this command
is not needed. When net devices are moved to new net, the ib devices are
also moved automically.
Per our discussion, if RoCE's net devices and ib devices are separated
in the different net, ib devices
can not work.
Zhu Yanjun
>
> Thanks
next prev parent reply other threads:[~2022-10-23 13:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 22:04 [PATCH 0/3] RDMA net namespace Zhu Yanjun
2022-10-23 13:04 ` Leon Romanovsky
2022-10-23 13:42 ` Yanjun Zhu [this message]
2022-10-23 16:45 ` Leon Romanovsky
2022-10-24 7:20 ` yanjun.zhu
2022-10-23 22:04 ` [PATCH 1/3] RDMA/core: Move ib device to the same net namespace with net device Zhu Yanjun
2022-10-23 22:04 ` [PATCH 2/3] RDMA/core: The legacy IB devices still work with shared/exclusive mode Zhu Yanjun
2022-10-23 22:04 ` [PATCH 3/3] RDMA/core: Get all the ib devices from net devices Zhu Yanjun
2022-10-24 1:10 ` [PATCH 0/3] RDMA net namespace Dust Li
2022-10-24 6:15 ` yanjun.zhu
2022-10-24 11:52 ` Dust Li
2022-10-24 13:12 ` Yanjun Zhu
2022-10-24 14:35 ` Dust Li
2022-10-24 16:41 ` Jason Gunthorpe
2022-10-25 2:51 ` Yanjun Zhu
2022-10-26 4:08 ` Dust Li
2022-10-26 15:01 ` Dust Li
2022-10-27 2:30 ` Dust Li
2022-10-27 2:54 ` yanjun.zhu
2022-10-27 3:01 ` Parav Pandit
2022-10-27 3:07 ` yanjun.zhu
2022-10-27 3:10 ` Parav Pandit
2022-10-27 3:17 ` yanjun.zhu
2022-10-27 3:21 ` Parav Pandit
2022-10-27 3:39 ` yanjun.zhu
2022-10-27 3:48 ` Parav Pandit
2022-10-27 6:01 ` yanjun.zhu
2022-10-27 14:06 ` Parav Pandit
2022-10-28 3:21 ` Yanjun Zhu
2022-10-28 3:31 ` Parav Pandit
2022-10-28 3:49 ` Yanjun Zhu
2022-10-28 3:58 ` Parav Pandit
2022-11-11 2:38 ` Yanjun Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac6228a7-52a6-3b80-6b22-c4444b67d360@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox