From: Leon Romanovsky <leonro@nvidia.com>
To: David Ahern <dsahern@kernel.org>
Cc: <stephen@networkplumber.org>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, David Ahern <dahern@nvidia.com>
Subject: Re: [PATCH iproute2-next v2 3/4] rdma: Allow netns to be specified by pid
Date: Wed, 13 May 2026 08:49:51 +0300 [thread overview]
Message-ID: <20260513054951.GB15586@unreal> (raw)
In-Reply-To: <20260512193412.32019-4-dsahern@kernel.org>
On Tue, May 12, 2026 at 01:34:06PM -0600, David Ahern wrote:
> From: David Ahern <dahern@nvidia.com>
>
> Update rdma dev to work like ip link where the netns can be a
> name or a pid by using netns_get_fd. Update man page and help
> accordingly.
>
> Signed-off-by: David Ahern <dahern@nvidia.com>
> ---
> man/man8/rdma-dev.8 | 3 ++-
> rdma/dev.c | 11 ++++-------
> 2 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/man/man8/rdma-dev.8 b/man/man8/rdma-dev.8
> index abc9f405ede5..34ea1c614ca4 100644
> --- a/man/man8/rdma-dev.8
> +++ b/man/man8/rdma-dev.8
> @@ -32,7 +32,7 @@ rdma-dev \- RDMA device configuration
> .B rdma dev set
> .RI "[ " DEV " ]"
> .BR netns
> -.BR NSNAME
> +.BR { NSNAME | PID }
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2026-05-13 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:34 [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid David Ahern
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 [this message]
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
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=20260513054951.GB15586@unreal \
--to=leonro@nvidia.com \
--cc=dahern@nvidia.com \
--cc=dsahern@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox