From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: David Ahern <dsahern@kernel.org>, Leon Romanovsky <leon@kernel.org>
Cc: zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Add network namespace support
Date: Thu, 26 Feb 2026 22:28:03 -0800 [thread overview]
Message-ID: <13d804be-0bef-41bb-b252-c31f62a0b4a0@linux.dev> (raw)
In-Reply-To: <c0887a43-f5ea-4e7b-8fb5-7322b76396a3@kernel.org>
在 2026/2/26 18:05, David Ahern 写道:
> On 2/26/26 5:06 PM, yanjun.zhu wrote:
>> The patch link is: https://github.com/zhuyj/linux/tree/6.19-net-namespace
> please send the patches; I cannot give comments to a github tree.
>
> Scanning the patches, I think you have over complicated what needs to be
> done.
>
> 1. socket lookups are not free. If the rxe module is going to own the
> socket, let it own the socket. See my patch with the net_generic way of
> retrieving the socket per namespace. <several patches later> Oh, you
> also bring in net_generic, so why make this so complicated?
Thanks, I will use net_generic later.
> 2. current code creates the socket for init_net at module load time. My
> patch changes it to first rxe link create and then leaves it enabled
> until the namespace is deleted. Why? Well, any solution trying to track
> how many devices are in the namespace is overly complicated. If an rxe
> is created once what are the odds it will be created again? This is a
> very specific type of workload. Besides, it makes the code very simple.
> I bet this is why my patch fails any test cases you have.
Yes. I will send out my commit very soon.
Thanks a lot.
Zhu Yanjun
>
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2026-02-27 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 17:26 [PATCH] RDMA/rxe: Add network namespace support David Ahern
2026-02-25 18:14 ` yanjun.zhu
2026-02-25 18:50 ` David Ahern
2026-02-25 21:07 ` yanjun.zhu
2026-02-26 6:47 ` Leon Romanovsky
2026-02-26 15:51 ` Zhu Yanjun
2026-02-26 16:06 ` David Ahern
2026-02-27 0:06 ` yanjun.zhu
2026-02-27 2:05 ` David Ahern
2026-02-27 6:28 ` Zhu Yanjun [this message]
2026-02-27 22:13 ` Yanjun.Zhu
2026-02-26 14:08 ` kernel test robot
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=13d804be-0bef-41bb-b252-c31f62a0b4a0@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=dsahern@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox