> Furthermore, the links are already there in sysfs, created by the PCI subsystem. > > /sys/class/net/ethX/device links to the PCI device entry for the PF device, which itself has symlinks to each of the VF devices. > > This patch just isn't necessary. I'm not talking about PF's pci device, because PF driver knows it. I'm talking about VF's. The root cause is PF cannot get VF's bdf, so it has no idea where VF is. IMO it's abnormal. Make symlinks is just a use case. When a userspace app only knows VF's bdf, it has no idea how to get into the VF's interface-like directories. (/sys/class/net/ethX/vf[1-7]) Because of: 1. Userspace app cannot get PF's bdf from VF's bdf 2. Userspace app cannot guess the interface name of pf(ethX) So a symlink from /sys/bus/pci/devices/xxxxx to /sys/class/net/ethX/vf[1-7] is useful. This is a real issue. Thanks for reply. -- Frank Pan Computer Science and Technology Tsinghua University -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
