From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Chuck Lever III <chuck.lever@oracle.com>,
Bob Pearson <rpearsonhpe@gmail.com>
Cc: Zhu Yanjun <yanjun.zhu@intel.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"parav@nvidia.com" <parav@nvidia.com>,
"lehrer@gmail.com" <lehrer@gmail.com>
Subject: Re: [PATCH v6.4-rc1 v5 0/8] Fix the problem that rxe can not work in net namespace
Date: Sun, 25 Jun 2023 08:54:09 +0800 [thread overview]
Message-ID: <c973ddac-2f7f-ca8d-49a0-3f490e7343a5@linux.dev> (raw)
In-Reply-To: <9DD4E3B8-7FA1-4054-8AC0-85FC96D710A7@oracle.com>
在 2023/6/25 1:32, Chuck Lever III 写道:
>> The GID of rxe can not be generated with lo. This is a problem.
> I agree, and would like to see a fix. It's obviously going to be a very
> useful use case for CI environments for upper layer storage protocols
> such as NFS and SMB, for instance.
>
>
>> Now Chuck Lever <cel@kernel.org> will fix it.
> My understanding is that, because RoCE allows more than one port per egress
> device, the mechanism for enabling rxe-on-lo is going to be different than
> it is for iWARP -- or it might not be possible at all. That's why my siw
> patches do not implement a fix for rxe.
>
> Jason needs to outline a mechanism for it so we can see what needs to be
> done. At which point, any interested party should be able to fix it.
Look forward to the fix.
Zhu Yanjun
>
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2023-06-25 0:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 7:56 [PATCH v6.4-rc1 v5 0/8] Fix the problem that rxe can not work in net namespace Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 1/8] RDMA/rxe: Creating listening sock in newlink function Zhu Yanjun
2023-06-20 17:16 ` Bob Pearson
2023-06-20 23:40 ` Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 2/8] RDMA/rxe: Support more rdma links in init_net Zhu Yanjun
2023-06-20 17:54 ` Bob Pearson
2023-06-20 23:51 ` Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 3/8] RDMA/nldev: Add dellink function pointer Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 4/8] RDMA/rxe: Implement dellink in rxe Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 5/8] RDMA/rxe: Replace global variable with sock lookup functions Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 6/8] RDMA/rxe: add the support of net namespace Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 7/8] RDMA/rxe: Add the support of net namespace notifier Zhu Yanjun
2023-05-08 7:56 ` [PATCH v6.4-rc1 v5 8/8] RDMA/rxe: Replace l_sk6 with sk6 in net namespace Zhu Yanjun
2023-06-21 21:09 ` [PATCH v6.4-rc1 v5 0/8] Fix the problem that rxe can not work " Bob Pearson
2023-06-21 21:27 ` Bob Pearson
2023-06-23 7:15 ` Zhu Yanjun
2023-06-23 12:59 ` Bob Pearson
2023-06-23 23:50 ` Zhu Yanjun
2023-06-24 17:03 ` Pearson, Robert B
2023-06-24 17:32 ` Chuck Lever III
2023-06-25 0:54 ` Zhu Yanjun [this message]
2023-06-25 0:53 ` Zhu Yanjun
2023-06-22 3:46 ` Zhu Yanjun
2023-06-23 7:09 ` Zhu Yanjun
2024-11-12 9:33 ` Cyclinder Kuo
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=c973ddac-2f7f-ca8d-49a0-3f490e7343a5@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=chuck.lever@oracle.com \
--cc=jgg@ziepe.ca \
--cc=lehrer@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@intel.com \
--cc=zyjzyj2000@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.