From: Leon Romanovsky <leon@kernel.org>
To: Zhu Yanjun <yanjun.zhu@intel.com>
Cc: yanjun.zhu@linux.dev, jgg@nvidia.com, leo@kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] RDMA/core: Fix a problem from rdma link in exclusive mode
Date: Tue, 11 Oct 2022 13:12:22 +0300 [thread overview]
Message-ID: <Y0VBhhhSfzRQ8GY9@unreal> (raw)
In-Reply-To: <20221011002545.1410247-1-yanjun.zhu@intel.com>
On Mon, Oct 10, 2022 at 08:25:45PM -0400, Zhu Yanjun wrote:
> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> 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.
>
> 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.
Thanks
next prev parent reply other threads:[~2022-10-11 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 2:40 [PATCH] rdma: not display the rdma link in other net namespace yanjun.zhu
2022-09-25 10:22 ` Yanjun Zhu
2022-09-27 10:34 ` Leon Romanovsky
2022-09-27 10:58 ` Yanjun Zhu
2022-09-28 6:04 ` Leon Romanovsky
2022-09-30 7:25 ` Yanjun Zhu
2022-10-06 12:53 ` Leon Romanovsky
2022-10-06 14:26 ` Yanjun Zhu
2022-10-06 16:21 ` Leon Romanovsky
2022-10-06 16:23 ` Jason Gunthorpe
2022-10-07 6:21 ` Leon Romanovsky
2022-10-07 6:56 ` Yanjun Zhu
2022-10-11 0:25 ` [RFC PATCH 1/1] RDMA/core: Fix a problem from rdma link in exclusive mode Zhu Yanjun
2022-10-11 10:12 ` Leon Romanovsky [this message]
2022-10-11 15:08 ` Yanjun Zhu
2022-10-13 8:30 ` yanjun.zhu
2022-10-09 10:20 ` [PATCH] rdma: not display the rdma link in other net namespace yanjun.zhu
2022-10-11 9:49 ` Leon Romanovsky
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=Y0VBhhhSfzRQ8GY9@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=leo@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@intel.com \
--cc=yanjun.zhu@linux.dev \
/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