diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2026-07-08 11:23:50 +0200 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2026-07-08 11:23:51 +0200 |
| commit | bcd2e8b40ef955038d9af137d3ebeb0de786d835 (patch) | |
| tree | 86e19c3050f3f843bd4f76a20b86b411bb04537d /tools/perf/scripts/python/stackcollapse.py | |
| parent | a6cfd2762eb18cde4eb34906599ffa7b07c2ed60 (diff) | |
| parent | a49ea2e042af96a7f028ef0972f03589df134eba (diff) | |
Merge branch 'devlink-extend-phys_port_name-controller-prefix-to-non-external-ports'
Tariq Toukan says:
====================
devlink: extend phys_port_name controller prefix to non-external ports
This series by Moshe includes the controller number in phys_port_name
for non-external ports with a non-zero controller, and updates the mlx5
driver to mark satellite PFs as non-external.
The controller prefix (c) in phys_port_name was previously only included
for ports marked as external. However, newer devices can have multiple
controllers within the DPU itself, even within a single host
environment. For example, a SmartNIC may have additional local PCI
physical functions that are managed by the eswitch but are not on an
external host. These ports use a non-zero controller number to
distinguish them from the eswitch manager's own functions, while the
external flag remains unset.
Patch 1 updates the devlink core to include the controller prefix in
phys_port_name for any non-zero controller, regardless of the external
flag. Documentation and kdoc are updated accordingly.
Patch 2 updates the mlx5 driver to set satellite PF devlink ports as
non-external, since they are local to the DPU. It also distinguishes
satellite PF SFs from host PF SFs when setting the external attribute.
====================
Link: https://patch.msgid.link/20260702111726.816985-1-tariqt@nvidia.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
