From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: jgg@ziepe.ca, leon@kernel.org, zyjzyj2000@gmail.com,
dsahern@kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Subject: Re: [PATCH v4 0/4] RDMA/rxe: Add the support that rxe can work in net namespace
Date: Sun, 8 Mar 2026 16:40:26 -0700 [thread overview]
Message-ID: <45947149-36ef-41f2-8ad0-aa3519344ce0@linux.dev> (raw)
In-Reply-To: <20260308233540.13382-1-yanjun.zhu@linux.dev>
在 2026/3/8 16:35, Zhu Yanjun 写道:
> Currently rxe does not work correctly in network namespaces.
>
> When the rdma_rxe module is loaded, a UDP socket listening on port
> 4791 is created in init_net. When users run:
>
> ip link add ... type rxe
>
> inside another network namespace, the RXE RDMA link is created but it
> cannot function properly because the underlying UDP socket belongs to
> init_net. Other network namespaces cannot use that socket.
>
> To address this issue, this series introduces net namespace support
> for rxe and moves socket management to be per network namespace.
>
> The series first introduces per-net namespace management for the IPv4
> and IPv6 sockets used by rxe. The sockets are created when the network
> namespace becomes active and are released when the namespace is
> destroyed.
>
> Based on this infrastructure, rxe RDMA links are then created and
> destroyed within each network namespace. This ensures that both the
> UDP sockets and RDMA links are correctly scoped to the namespace in
> which they are used.
>
> With these changes, rxe RDMA links can be created and used both in
> init_net and in other network namespaces, and resources are properly
> cleaned up during namespace teardown.
>
> The series also includes a selftest to verify RXE functionality in
> network namespaces.
The selftest result is as below:
"
# make -C tools/testing/selftests/ TARGETS=rdma run_tests
make: Entering directory '/root/Development/linux/tools/testing/selftests'
make[1]: Nothing to be done for 'all'.
TAP version 13
1..4
# timeout set to 45
# selftests: rdma: rxe_rping_between_netns.sh
# server DISCONNECT EVENT...
# wait for RDMA_READ_ADV state 10
ok 1 selftests: rdma: rxe_rping_between_netns.sh
# timeout set to 45
# selftests: rdma: rxe_ipv6.sh
ok 2 selftests: rdma: rxe_ipv6.sh
# timeout set to 45
# selftests: rdma: rxe_socket_with_netns.sh
ok 3 selftests: rdma: rxe_socket_with_netns.sh
# timeout set to 45
# selftests: rdma: rxe_test_NETDEV_UNREGISTER.sh
ok 4 selftests: rdma: rxe_test_NETDEV_UNREGISTER.sh
make: Leaving directory '/root/Development/linux/tools/testing/selftests'
"
Zhu Yanjun
>
> V3 -> V4: Squash all the changes about rxe_ns.c/h into one commit.
> V2 -> V3: Fix build warnings
> V1 -> V2: Fix the problems based on David Ahern.
>
>
> Zhu Yanjun (4):
> RDMA/nldev: Add dellink function pointer
> RDMA/rxe: Add net namespace support for IPv4/IPv6 sockets
> RDMA/rxe: Support RDMA link creation and destruction per net namespace
> RDMA/rxe: Add testcase for net namespace rxe
>
> MAINTAINERS | 1 +
> drivers/infiniband/core/nldev.c | 6 +
> drivers/infiniband/sw/rxe/Makefile | 3 +-
> drivers/infiniband/sw/rxe/rxe.c | 38 ++++-
> drivers/infiniband/sw/rxe/rxe_net.c | 145 +++++++++++++-----
> drivers/infiniband/sw/rxe/rxe_net.h | 9 +-
> drivers/infiniband/sw/rxe/rxe_ns.c | 136 ++++++++++++++++
> drivers/infiniband/sw/rxe/rxe_ns.h | 17 ++
> include/rdma/rdma_netlink.h | 2 +
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/rdma/Makefile | 7 +
> tools/testing/selftests/rdma/config | 3 +
> tools/testing/selftests/rdma/rxe_ipv6.sh | 47 ++++++
> .../selftests/rdma/rxe_rping_between_netns.sh | 57 +++++++
> .../selftests/rdma/rxe_socket_with_netns.sh | 64 ++++++++
> .../rdma/rxe_test_NETDEV_UNREGISTER.sh | 38 +++++
> 16 files changed, 527 insertions(+), 47 deletions(-)
> create mode 100644 drivers/infiniband/sw/rxe/rxe_ns.c
> create mode 100644 drivers/infiniband/sw/rxe/rxe_ns.h
> create mode 100644 tools/testing/selftests/rdma/Makefile
> create mode 100644 tools/testing/selftests/rdma/config
> create mode 100755 tools/testing/selftests/rdma/rxe_ipv6.sh
> create mode 100755 tools/testing/selftests/rdma/rxe_rping_between_netns.sh
> create mode 100755 tools/testing/selftests/rdma/rxe_socket_with_netns.sh
> create mode 100755 tools/testing/selftests/rdma/rxe_test_NETDEV_UNREGISTER.sh
>
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2026-03-08 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 23:35 [PATCH v4 0/4] RDMA/rxe: Add the support that rxe can work in net namespace Zhu Yanjun
2026-03-08 23:35 ` [PATCH v4 1/4] RDMA/nldev: Add dellink function pointer Zhu Yanjun
2026-03-08 23:35 ` [PATCH v4 2/4] RDMA/rxe: Add net namespace support for IPv4/IPv6 sockets Zhu Yanjun
2026-03-09 18:54 ` David Ahern
2026-03-10 0:59 ` yanjun.zhu
2026-03-08 23:35 ` [PATCH v4 3/4] RDMA/rxe: Support RDMA link creation and destruction per net namespace Zhu Yanjun
2026-03-09 18:54 ` David Ahern
2026-03-10 0:57 ` yanjun.zhu
2026-03-08 23:35 ` [PATCH v4 4/4] RDMA/rxe: Add testcase for net namespace rxe Zhu Yanjun
2026-03-08 23:40 ` Zhu Yanjun [this message]
2026-03-09 18:55 ` [PATCH v4 0/4] RDMA/rxe: Add the support that rxe can work in net namespace David Ahern
2026-03-10 0:55 ` yanjun.zhu
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=45947149-36ef-41f2-8ad0-aa3519344ce0@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=dsahern@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kselftest@vger.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 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.