Home
last modified time | relevance | path

Searched hist:"51 c1df83e35ce0e24ca10037c73245cb4c8ac11a" (Results 1 – 5 of 5) sorted by relevance

/linux/drivers/net/ethernet/netronome/nfp/
H A Dnfp_net_debugfs.cdiff 51c1df83e35ce0e24ca10037c73245cb4c8ac11a Tue May 22 07:12:55 CEST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: assign vNIC id as phys_port_name of vNICs which are not ports

When NFP is modelled as a switch we assign phys_port_name to respective
port(representor )s:

vNIC0 - | - PF port (pf%d) MAC/PHY (p%d[s%d]) - |E==

In most cases there is only one vNIC for communication with the switch.
If there is more than one we need to be able to identify them. Use %d
as phys_port_name of the vNICs.

We don't have to pass ID to nfp_net_debugfs_vnic_add() separately any
more.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dnfp_netvf_main.cdiff 51c1df83e35ce0e24ca10037c73245cb4c8ac11a Tue May 22 07:12:55 CEST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: assign vNIC id as phys_port_name of vNICs which are not ports

When NFP is modelled as a switch we assign phys_port_name to respective
port(representor )s:

vNIC0 - | - PF port (pf%d) MAC/PHY (p%d[s%d]) - |E==

In most cases there is only one vNIC for communication with the switch.
If there is more than one we need to be able to identify them. Use %d
as phys_port_name of the vNICs.

We don't have to pass ID to nfp_net_debugfs_vnic_add() separately any
more.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dnfp_net_main.cdiff 51c1df83e35ce0e24ca10037c73245cb4c8ac11a Tue May 22 07:12:55 CEST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: assign vNIC id as phys_port_name of vNICs which are not ports

When NFP is modelled as a switch we assign phys_port_name to respective
port(representor )s:

vNIC0 - | - PF port (pf%d) MAC/PHY (p%d[s%d]) - |E==

In most cases there is only one vNIC for communication with the switch.
If there is more than one we need to be able to identify them. Use %d
as phys_port_name of the vNICs.

We don't have to pass ID to nfp_net_debugfs_vnic_add() separately any
more.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dnfp_net.hdiff 51c1df83e35ce0e24ca10037c73245cb4c8ac11a Tue May 22 07:12:55 CEST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: assign vNIC id as phys_port_name of vNICs which are not ports

When NFP is modelled as a switch we assign phys_port_name to respective
port(representor )s:

vNIC0 - | - PF port (pf%d) MAC/PHY (p%d[s%d]) - |E==

In most cases there is only one vNIC for communication with the switch.
If there is more than one we need to be able to identify them. Use %d
as phys_port_name of the vNICs.

We don't have to pass ID to nfp_net_debugfs_vnic_add() separately any
more.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dnfp_net_common.cdiff 51c1df83e35ce0e24ca10037c73245cb4c8ac11a Tue May 22 07:12:55 CEST 2018 Jakub Kicinski <jakub.kicinski@netronome.com> nfp: assign vNIC id as phys_port_name of vNICs which are not ports

When NFP is modelled as a switch we assign phys_port_name to respective
port(representor )s:

vNIC0 - | - PF port (pf%d) MAC/PHY (p%d[s%d]) - |E==

In most cases there is only one vNIC for communication with the switch.
If there is more than one we need to be able to identify them. Use %d
as phys_port_name of the vNICs.

We don't have to pass ID to nfp_net_debugfs_vnic_add() separately any
more.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>