public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "yanjun.zhu" <yanjun.zhu@linux.dev>
Cc: David Ahern <dsahern@kernel.org>,
	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 08:47:55 +0200	[thread overview]
Message-ID: <20260226064755.GA12611@unreal> (raw)
In-Reply-To: <88b82e8b-40da-46cf-bb41-2c346bd28c70@linux.dev>

On Wed, Feb 25, 2026 at 01:07:12PM -0800, yanjun.zhu wrote:
> On 2/25/26 10:50 AM, David Ahern wrote:
> > On 2/25/26 11:14 AM, yanjun.zhu wrote:
> > > On 2/25/26 9:26 AM, David Ahern wrote:
> > > > Allow rxe to work across network namespaces by making the sockets
> > > > per namespace using net_generic. Defer socket initialization until
> > > > a device is created in the namespace.
> > > 
> > > https://github.com/zhuyj/linux/tree/upstream/6.14-net-namespace
> > > 
> > > Do you make tests with the above link?
> > 
> > no. I had no knowledge of that branch until this moment. It is almost 12
> > months old, so not sure the relevance if it is not being actively fixed
> > on top of tree.
> > 
> > > 
> > > Compared with the net namespace in the above link, what is the
> > > difference between this commit and the above link?
> > > 
> > 
> > no idea. This patch was in our tree at enfabrica dating back to 2021.
> > Someone started looking into automated tests with rxe, so I pulled it
> > from the tree, rebased to 7.0 and sent it out.
> > 
> 
> https://patchwork.kernel.org/project/linux-rdma/cover/20230624073927.707915-1-yanjun.zhu@intel.com/
> 
> In the above link, there is some testcases for the link
> https://github.com/zhuyj/linux/tree/upstream/6.14-net-namespace.
> 
> I am wondering if this commit can pass all the testcases or not.

Zhu,

It is a bit unreasonable to expect a random RXE contributor to compare
against something that lives out‑of‑tree. Please feel free to pick up that
patch and run it through your tests.

Thanks

> 
> Thanks a lot.
> Zhu Yanjun
> 
> 

  reply	other threads:[~2026-02-26  6:48 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 [this message]
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
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=20260226064755.GA12611@unreal \
    --to=leon@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjun.zhu@linux.dev \
    --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