From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com
Subject: [PATCH iproute2-next 0/3] devlink: show devlink instance index in dev output
Date: Mon, 16 Mar 2026 16:44:15 +0100 [thread overview]
Message-ID: <20260316154418.625026-1-jiri@resnulli.us> (raw)
From: Jiri Pirko <jiri@nvidia.com>
Support for identifying devlink instances by a unique index was recently
added on the kernel side:
https://lore.kernel.org/all/20260312100407.551173-1-jiri@resnulli.us/
This patchset adds the necessary userspace support.
First, as a dependency, introduce a fallback for mnl_attr_get_uint()
to handle the NLA_UINT variable-width attribute type used by the
kernel for the index, with backward compatibility for older libmnl
versions.
Then, display the devlink instance index in dev show output when
the kernel provides it.
Jiri Pirko (3):
update kernel headers
mnl: add fallback implementation for mnl_attr_get_uint()
devlink: show devlink instance index in dev output
configure | 22 ++++++++++++++++++++++
devlink/devlink.c | 6 +++++-
include/mnl_utils.h | 4 ++++
include/uapi/linux/devlink.h | 4 ++++
lib/mnl_utils.c | 17 +++++++++++++++++
5 files changed, 52 insertions(+), 1 deletion(-)
--
2.51.1
next reply other threads:[~2026-03-16 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 15:44 Jiri Pirko [this message]
2026-03-16 15:44 ` [PATCH iproute2-next 1/3] update kernel headers Jiri Pirko
2026-03-16 15:44 ` [PATCH iproute2-next 2/3] mnl: add fallback implementation for mnl_attr_get_uint() Jiri Pirko
2026-03-16 16:12 ` Stephen Hemminger
2026-03-17 8:17 ` Jiri Pirko
2026-03-18 2:31 ` David Ahern
2026-03-16 15:44 ` [PATCH iproute2-next 3/3] devlink: show devlink instance index in dev output Jiri Pirko
2026-03-23 0:20 ` [PATCH iproute2-next 0/3] " 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=20260316154418.625026-1-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=dsahern@gmail.com \
--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