devlink: Use controller while building phys_port_name
authorParav Pandit <parav@nvidia.com>
Wed, 9 Sep 2020 04:50:38 +0000 (07:50 +0300)
committerDavid S. Miller <davem@davemloft.net>
Wed, 9 Sep 2020 21:19:55 +0000 (14:19 -0700)
commit66b17082d10a3b806eec3da8fdebe8a9cd2c6612
treec62fbb8405a0768e0a73a4e8043fcd6e8abd0343
parent3a2d9588c4f79adae6a0e986b64ebdd5b38085c6
devlink: Use controller while building phys_port_name

Now that controller number attribute is available, use it when
building phsy_port_name for external controller ports.

An example devlink port and representor netdev name consist of controller
annotation for external controller with controller number = 1,
for a VF 1 of PF 0:

$ devlink port show pci/0000:06:00.0/2
pci/0000:06:00.0/2: type eth netdev ens2f0c1pf0vf1 flavour pcivf controller 1 pfnum 0 vfnum 1 external true splittable false
  function:
    hw_addr 00:00:00:00:00:00

$ devlink port show pci/0000:06:00.0/2 -jp
{
    "port": {
        "pci/0000:06:00.0/2": {
            "type": "eth",
            "netdev": "ens2f0c1pf0vf1",
            "flavour": "pcivf",
            "controller": 1,
            "pfnum": 0,
            "vfnum": 1,
            "external": true,
            "splittable": false,
            "function": {
                "hw_addr": "00:00:00:00:00:00"
            }
        }
    }
}

Controller number annotation is skipped for non external controllers to
maintain backward compatibility.

Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/core/devlink.c