From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leo@kernel.org>,
linux-rdma@vger.kernel.org, jgg@nvidia.com
Subject: Re: [PATCH] rdma: not display the rdma link in other net namespace
Date: Thu, 6 Oct 2022 22:26:33 +0800 [thread overview]
Message-ID: <99a4b7ea-64df-7de4-2d7a-52e797644e71@linux.dev> (raw)
In-Reply-To: <Yz7PsMhkWMH0HXjt@unreal>
在 2022/10/6 20:53, Leon Romanovsky 写道:
> On Fri, Sep 30, 2022 at 03:25:00PM +0800, Yanjun Zhu wrote:
>> 在 2022/9/28 14:04, Leon Romanovsky 写道:
>>> On Tue, Sep 27, 2022 at 06:58:50PM +0800, Yanjun Zhu wrote:
>>>> 在 2022/9/27 18:34, Leon Romanovsky 写道:
>>>>> On Sun, Sep 25, 2022 at 10:40:33PM -0400, yanjun.zhu@linux.dev wrote:
>>>>>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
> <...>
>
>> Is it better to append "exclusive" or "shared" in the end of the line?
> No, exclusive/shared is global property, applied to all links.
OK.
When running "rdma link show", there is no difference between shared and
exclusive.
Is it acceptable?
And in exclusive mode, a rdma link that can not be accessed in net
namespace A still
appears in net namespace A when running "rdma link show" in net namespace A.
The above is different from others in net namespace.
For example, in net namespace, if net device NIC0 is moved to net
namespace B from net namespace A,
this NIC0 will not appear in net namespace A when running "ip link"
command in net namespace A.
Is it a problem?
Zhu Yanjun
>
> Thanks
next prev parent reply other threads:[~2022-10-06 14:26 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 [this message]
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
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=99a4b7ea-64df-7de4-2d7a-52e797644e71@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@nvidia.com \
--cc=leo@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).