From: David Ahern <dsahern@kernel.org>
To: Leon Romanovsky <leonro@nvidia.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, David Ahern <dahern@nvidia.com>
Subject: Re: [PATCH iproute2-next v2 4/4] devlink: Drop now duplicate pid fallback for netns
Date: Wed, 13 May 2026 19:06:55 -0600 [thread overview]
Message-ID: <b8ef4424-112e-4ed4-b67a-05ace9c258b3@kernel.org> (raw)
In-Reply-To: <20260513054045.GY15586@unreal>
On 5/12/26 11:40 PM, Leon Romanovsky wrote:
>
> You can also remove netns_is_pid from struct dl_opts.
I left it because of the uapi. I will wait for any more comments, and if
that is the only one I can add the removal when I apply.
>
> It is unfortunate that devlink implements DEVLINK_ATTR_NETNS_PID in
> the kernel, given that user space can provide this functionality
> with trivial effort.
yea. really stunned that uapi exists.
prev parent reply other threads:[~2026-05-14 1:06 UTC|newest]
Thread overview: 10+ 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
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 [this message]
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=b8ef4424-112e-4ed4-b67a-05ace9c258b3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox