Thu, Feb 05, 2026 at 03:28:30PM +0100, tariqt@nvidia.com wrote:

From: Or Har-Toov <redacted>

The device-level "resource show" displays max_local_SFs and
max_external_SFs without indicating which port each resource belongs
to. Users cannot determine the controller number and pfnum associated
with each SF pool.

Register max_SFs resource on the Host PF representor port to expose
per-port SF limits. Users can correlate the port resource with the
controller number and pfnum shown in 'devlink port show'.

Future patches will introduce an ECPF that manages multiple PFs,
where each PF has its own SF pool.

Example usage:

 $ 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

 $ 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 show pci/0000:03:00.0/196608
 pci/0000:03:00.0/196608: type eth netdev pf0hpf flavour pcipf
   controller 1 pfnum 0 external true splittable false
   function:
     hw_addr b8:3f:d2:e1:8f:dc roce enable max_io_eqs 120

We can create up to 20 SFs over devlink port pci/0000:03:00.0/196608,
with pfnum 0 and controller 1.

Signed-off-by: Or Har-Toov <redacted>
Reviewed-by: Shay Drori <redacted>
Reviewed-by: Moshe Shemesh <redacted>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Reviewed-by: Jiri Pirko <redacted>