From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Donald Hunter <donald.hunter@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
Saeed Mahameed <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Shuah Khan <shuah@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
Gal Pressman <gal@nvidia.com>, Moshe Shemesh <moshe@nvidia.com>,
Shay Drori <shayd@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: [PATCH net-next V2 0/7] devlink: add per-port resource support
Date: Thu, 5 Feb 2026 16:28:26 +0200 [thread overview]
Message-ID: <20260205142833.1727929-1-tariqt@nvidia.com> (raw)
Hi,
This series adds devlink per-port resource support.
See detailed description by Or below [1].
Regards,
Tariq
[1]
Currently, devlink resources are only available at the device level.
However, some resources are inherently per-port, such as the maximum
number of subfunctions (SFs) that can be created on a specific PF port.
This limitation prevents user space from obtaining accurate per-port
capacity information.
This series adds infrastructure for per-port resources in devlink core
and implements it in the mlx5 driver to expose the max_SFs resource on
PF devlink ports.
Patch #1 refactors resource functions to be generic
Patch #2 adds port-level resource registration functions
Patch #3 adds port resource netlink command
Patch #4 registers SF resource on PF port representor in mlx5
Patch #5 adds port resource registration to netdevsim for testing
Patch #6 adds selftest for devlink port resources
Patch #7 adds documentation for port-level resources
With this series (and upcoming userspace patches), users can query
per-port resources:
$ devlink port resource show pci/0000:03:00.0/196608
pci/0000:03:00.0/196608:
name max_SFs size 20 unit entry
$ devlink port resource show
pci/0000:03:00.0/196608:
name max_SFs size 20 unit entry
pci/0000:03:00.1/262144:
name max_SFs size 20 unit entry
Userspace patches for iproute2:
https://github.com/ohartoov/iproute2/tree/port_resource
V2:
- Skip selftest on old userspace that doesn't have the devlink
port resource command.
- Add link to the userspace patch.
- Rename internal helper functions to follow kernel __ prefix
convention.
- Split first patch into three logical commits.
- Change names with "res" to "resource".
- Change netdevsim test resource to be generic and not with max_sfs.
- Change "max_sfs" to "max_SFs" in documentation file.
- V1 link: https://lore.kernel.org/all/20260203071033.1709445-1-tariqt@nvidia.com/
Or Har-Toov (7):
devlink: Refactor resource functions to be generic
devlink: Add port-level resource registration infrastructure
devlink: Add port resource netlink command
net/mlx5: Register SF resource on PF port representor
netdevsim: Add devlink port resource registration
selftest: netdevsim: Add devlink port resource test
devlink: Document port-level resources
Documentation/netlink/specs/devlink.yaml | 23 ++
.../networking/devlink/devlink-resource.rst | 36 +++
.../net/ethernet/mellanox/mlx5/core/devlink.h | 4 +
.../mellanox/mlx5/core/esw/devlink_port.c | 37 +++
drivers/net/netdevsim/dev.c | 23 +-
drivers/net/netdevsim/netdevsim.h | 4 +
include/net/devlink.h | 8 +
include/uapi/linux/devlink.h | 3 +
net/devlink/netlink.c | 2 +-
net/devlink/netlink_gen.c | 32 +-
net/devlink/netlink_gen.h | 6 +-
net/devlink/port.c | 3 +
net/devlink/resource.c | 281 ++++++++++++++----
.../drivers/net/netdevsim/devlink.sh | 37 ++-
14 files changed, 441 insertions(+), 58 deletions(-)
base-commit: 021718d2cc1a2df2f53b06968fa89280199371bd
--
2.44.0
next reply other threads:[~2026-02-05 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 14:28 Tariq Toukan [this message]
2026-02-05 14:28 ` [PATCH net-next V2 1/7] devlink: Refactor resource functions to be generic Tariq Toukan
2026-02-06 9:19 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 2/7] devlink: Add port-level resource registration infrastructure Tariq Toukan
2026-02-06 9:21 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 3/7] devlink: Add port resource netlink command Tariq Toukan
2026-02-06 9:33 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 4/7] net/mlx5: Register SF resource on PF port representor Tariq Toukan
2026-02-06 9:36 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 5/7] netdevsim: Add devlink port resource registration Tariq Toukan
2026-02-06 9:36 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 6/7] selftest: netdevsim: Add devlink port resource test Tariq Toukan
2026-02-06 9:37 ` Jiri Pirko
2026-02-05 14:28 ` [PATCH net-next V2 7/7] devlink: Document port-level resources Tariq Toukan
2026-02-06 9:42 ` Jiri Pirko
2026-02-06 0:17 ` [PATCH net-next V2 0/7] devlink: add per-port resource support Jakub Kicinski
2026-02-06 9:24 ` Jiri Pirko
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=20260205142833.1727929-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=shuah@kernel.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