Commit 290f54db authored by Jakub Kicinski's avatar Jakub Kicinski Committed by David S. Miller

nfp: use split in naming of PCIe PF ports

PCI PFs can host more than one logical endpoint.  In NFP terms
this means having more than one vNIC for PCIe PF.  The vNICs
are usually corresponding 1:1 to Ethernet ports.  In core NIC
we use the legacy idea of vNIC *being* the Ethernet port,
hence netdevs put pX(sY) in their phys_port_name, like Ethernet
ports would.  When ASIC ports are fully represented we need to
be able to name different PCIe PF ports, too.  Use a scheme
similar to Ethernet ports - pfXsY, for PCIe PF number X,
sub-port Y.
Signed-off-by: default avatarJakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: default avatarDirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 1f700367
...@@ -109,6 +109,8 @@ nfp_abm_spawn_repr(struct nfp_app *app, struct nfp_abm_link *alink, ...@@ -109,6 +109,8 @@ nfp_abm_spawn_repr(struct nfp_app *app, struct nfp_abm_link *alink,
goto err_free_port; goto err_free_port;
} else { } else {
port->pf_id = alink->abm->pf_id; port->pf_id = alink->abm->pf_id;
port->pf_split = app->pf->max_data_vnics > 1;
port->pf_split_id = alink->id;
port->vnic = alink->vnic->dp.ctrl_bar; port->vnic = alink->vnic->dp.ctrl_bar;
} }
......
...@@ -181,7 +181,11 @@ nfp_port_get_phys_port_name(struct net_device *netdev, char *name, size_t len) ...@@ -181,7 +181,11 @@ nfp_port_get_phys_port_name(struct net_device *netdev, char *name, size_t len)
eth_port->label_subport); eth_port->label_subport);
break; break;
case NFP_PORT_PF_PORT: case NFP_PORT_PF_PORT:
n = snprintf(name, len, "pf%d", port->pf_id); if (!port->pf_split)
n = snprintf(name, len, "pf%d", port->pf_id);
else
n = snprintf(name, len, "pf%ds%d", port->pf_id,
port->pf_split_id);
break; break;
case NFP_PORT_VF_PORT: case NFP_PORT_VF_PORT:
n = snprintf(name, len, "pf%dvf%d", port->pf_id, port->vf_id); n = snprintf(name, len, "pf%dvf%d", port->pf_id, port->vf_id);
......
...@@ -82,6 +82,8 @@ enum nfp_port_flags { ...@@ -82,6 +82,8 @@ enum nfp_port_flags {
* @eth_stats: for %NFP_PORT_PHYS_PORT MAC stats if available * @eth_stats: for %NFP_PORT_PHYS_PORT MAC stats if available
* @pf_id: for %NFP_PORT_PF_PORT, %NFP_PORT_VF_PORT ID of the PCI PF (0-3) * @pf_id: for %NFP_PORT_PF_PORT, %NFP_PORT_VF_PORT ID of the PCI PF (0-3)
* @vf_id: for %NFP_PORT_VF_PORT ID of the PCI VF within @pf_id * @vf_id: for %NFP_PORT_VF_PORT ID of the PCI VF within @pf_id
* @pf_split: for %NFP_PORT_PF_PORT %true if PCI PF has more than one vNIC
* @pf_split_id:for %NFP_PORT_PF_PORT ID of PCI PF vNIC (valid if @pf_split)
* @vnic: for %NFP_PORT_PF_PORT, %NFP_PORT_VF_PORT vNIC ctrl memory * @vnic: for %NFP_PORT_PF_PORT, %NFP_PORT_VF_PORT vNIC ctrl memory
* @port_list: entry on pf's list of ports * @port_list: entry on pf's list of ports
*/ */
...@@ -108,6 +110,8 @@ struct nfp_port { ...@@ -108,6 +110,8 @@ struct nfp_port {
struct { struct {
unsigned int pf_id; unsigned int pf_id;
unsigned int vf_id; unsigned int vf_id;
bool pf_split;
unsigned int pf_split_id;
u8 __iomem *vnic; u8 __iomem *vnic;
}; };
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment