public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "yanjun.zhu" <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 16:06:01 -0800	[thread overview]
Message-ID: <8098445a-c778-4b11-be88-6243aba98268@linux.dev> (raw)
In-Reply-To: <8ed32ed9-3931-4b2b-8f44-0023aa998b5c@kernel.org>

On 2/26/26 8:06 AM, David Ahern wrote:
> On 2/26/26 8:51 AM, Zhu Yanjun wrote:
>> Thanks a lot for your reply.  I’ve already submitted a similar patch
>> earlier.
> 
> In Jan 2021, rxe had no network namespace support. We fixed that and
> carried a patch (in stealth mode at the time).
> 
> In Feb 2026, rxe in Linus' master and rdma-next do not have network
> namespace support. I sent our well tested solution that works out of the
> box with behavior similar to how init_net works.
> 
> If you are interested in your design approach getting merged, then make
> it happen for 7.0-next. If you do not have the time to commit to it now,
> then step back and let this patch move forward. That is how Linux works
> - post ready-to-merge patches, not intentions.

Hi, David

Thank you for your feedback and for pushing this forward.

I completely agree that "ready-to-merge patches" are what drive the 
kernel forward. To that end, I have just finished rebasing and updating 
my implementation from 6.14 to the current 6.19-rc (and it’s ready for 
7.0-next).

I have full respect for your long-standing work on this. Since we both 
have functional solutions now, I suggest we quickly compare the design.

My goal is the same as yours: to finally get netns support into rxe for 
7.0. I will post my updated patch set shortly so the maintainers can 
evaluate both.

The patch link is: https://github.com/zhuyj/linux/tree/6.19-net-namespace

Please code review.

Best regards,
Zhu Yanjun

> 


  reply	other threads:[~2026-02-27  0:06 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 [this message]
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=8098445a-c778-4b11-be88-6243aba98268@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