Virtual Functions
| Bus |
Name |
Associated interface |
| 0000:c0:11.0 |
Ethernet Adaptive Virtual Function |
eth0 |
| 0000:c0:11.1 |
Ethernet Adaptive Virtual Function |
eth0 |
| 0000:c0:11.2 |
Ethernet Adaptive Virtual Function |
eth0 |
I see two ways it could be done:
By checking the memory mapping under lshw -c network
physical interfaces on a card share the same iomemory regions (always?), and the bus address start
virtual interfaces use memory regions from physical card's memory space
Using files under /sys/bus/pci/devices in a manner similar to this script https://github.com/OpenVisualCloud/Media-Transport-Library/blob/main/script/nicctl.sh (BSD-3-Clause)
Split from this original Issue: #377
Virtual Functions
I see two ways it could be done:
By checking the memory mapping under lshw -c network
physical interfaces on a card share the same iomemory regions (always?), and the bus address start
virtual interfaces use memory regions from physical card's memory space
Using files under /sys/bus/pci/devices in a manner similar to this script https://github.com/OpenVisualCloud/Media-Transport-Library/blob/main/script/nicctl.sh (BSD-3-Clause)
Split from this original Issue: #377