From: David Ahern <dsahern@kernel.org>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org, leonro@nvidia.com,
linux-rdma@vger.kernel.org, David Ahern <dahern@nvidia.com>
Subject: [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid
Date: Tue, 12 May 2026 13:34:03 -0600 [thread overview]
Message-ID: <20260512193412.32019-1-dsahern@kernel.org> (raw)
From: David Ahern <dahern@nvidia.com>
Avoid the extra hurdle of creating an entry in /var/run/netns
and allow the netns argument to be a name or a pid.
v2
- update netns_get_fd to handle the pid fallback
- update devlink code
David Ahern (4):
namespace: Add fallback to netns by pid
iplink: Drop pid fallback code for netns
rdma: Allow netns to be specified by pid
devlink: Drop now duplicate pid fallback for netns
devlink/devlink.c | 25 +++++++------------------
ip/iplink.c | 10 +---------
lib/namespace.c | 28 +++++++++++++++++++++-------
man/man8/rdma-dev.8 | 3 ++-
rdma/dev.c | 11 ++++-------
5 files changed, 35 insertions(+), 42 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-12 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:34 David Ahern [this message]
2026-05-12 19:34 ` [PATCH iproute2-next v2 1/4] namespace: Add fallback to netns by pid David Ahern
2026-05-13 5:49 ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 2/4] iplink: Drop pid fallback code for netns David Ahern
2026-05-13 5:49 ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 3/4] rdma: Allow netns to be specified by pid David Ahern
2026-05-13 5:49 ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 4/4] devlink: Drop now duplicate pid fallback for netns David Ahern
2026-05-13 5:40 ` Leon Romanovsky
2026-05-14 1:06 ` David Ahern
2026-05-15 19:30 ` [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid patchwork-bot+netdevbpf
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=20260512193412.32019-1-dsahern@kernel.org \
--to=dsahern@kernel.org \
--cc=dahern@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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.