[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191107153836.29c09400@cakuba.netronome.com>
Date: Thu, 7 Nov 2019 15:38:36 -0500
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Parav Pandit <parav@...lanox.com>
Cc: alex.williamson@...hat.com, davem@...emloft.net,
kvm@...r.kernel.org, netdev@...r.kernel.org, saeedm@...lanox.com,
kwankhede@...dia.com, leon@...nel.org, cohuck@...hat.com,
jiri@...lanox.com, linux-rdma@...r.kernel.org
Subject: Re: [PATCH net-next 12/19] devlink: Introduce mdev port flavour
On Thu, 7 Nov 2019 10:08:27 -0600, Parav Pandit wrote:
> Introduce a new mdev port flavour for mdev devices.
> PF.
> Prepare such port's phys_port_name using unique mdev alias.
>
> An example output for eswitch ports with one physical port and
> one mdev port:
>
> $ devlink port show
> pci/0000:06:00.0/65535: type eth netdev p0 flavour physical port 0
> pci/0000:06:00.0/32768: type eth netdev p1b0348cf880a flavour mdev alias 1b0348cf880a
Surely those devices are anchored in on of the PF (or possibly VFs)
that should be exposed here from the start.
> Signed-off-by: Parav Pandit <parav@...lanox.com>
> @@ -6649,6 +6678,9 @@ static int __devlink_port_phys_port_name_get(struct devlink_port *devlink_port,
> n = snprintf(name, len, "pf%uvf%u",
> attrs->pci_vf.pf, attrs->pci_vf.vf);
> break;
> + case DEVLINK_PORT_FLAVOUR_MDEV:
> + n = snprintf(name, len, "p%s", attrs->mdev.mdev_alias);
Didn't you say m$alias in the cover letter? Not p$alias?
> + break;
> }
>
> if (n >= len)
Powered by blists - more mailing lists