Thread (24 messages) 24 messages, 5 authors, 2021-01-26

Re: [net-next V9 03/14] devlink: Support add and delete devlink port

From: Jacob Keller <jacob.e.keller@intel.com>
Date: 2021-01-22 21:25:14
Also in: linux-rdma


On 1/21/2021 7:31 PM, Parav Pandit wrote:
quoted
From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
Sent: Friday, January 22, 2021 2:21 AM
quoted
$ devlink port show
pci/0000:06:00.0/65535: type eth netdev ens2f0np0 flavour physical
port 0 splittable false

$ devlink port add pci/0000:06:00.0 flavour pcisf pfnum 0 sfnum 88
Do we need to specify pfnum when adding a SF port? Isn't this redundant?
Isn't there a 1:1 mapping between the pci device and a pfnum?
No. it's not entirely redundant.
Currently in most cases today it is same function number as that of PCI device.
Netronome has one devlink instance that represents multiple PCI devices.
I am curious how this is done. I looked at doing this for ice but it
became incredibly problematic because of interacting across multiple
PCIe drivers.. Hmm. I'll have to go look at how this is handled in the
netronome driver.

Thanks,
Jake
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help