summaryrefslogtreecommitdiffstats
path: root/NEWS
diff options
context:
space:
mode:
authorStuart Hayes <stuart_hayes@dell.com>2018-01-18 21:14:56 +0100
committerStuart Hayes <stuart_hayes@dell.com>2018-03-26 20:00:43 +0200
commit6bc04997b6eab35d1cb9fa73889892702c27be09 (patch)
tree15c218df05bdfb8309b4513b56d94bc08dcecc22 /NEWS
parentudev: net_id: Improve predictable names for SR-IOV virtual devices (diff)
downloadsystemd-6bc04997b6eab35d1cb9fa73889892702c27be09.tar.xz
systemd-6bc04997b6eab35d1cb9fa73889892702c27be09.zip
udev: net_id: Improve predictable names for NPAR devices
NPAR is a technology that allows a single network interface to be divided into number of partitions. The partitions show up as functions on the same PCI device... when there are more than 8 functions, ARI (alternative routing-ID interpretation) is used. With ARI is enabled, the 8 bit field that normally has 5 bits for the PCI device and 3 bits for the PCI function is instead interpreted as (implicit) device 0, with 8 bits for the function number. Because the linux kernel exposes the PCI device/function numbers to userspace the same regardless of whether ARI is enabled, systemd predictable device naming can generate unpredictable names in this case, because network names using the PCI slot use the function number, but not the device number, causing systemd to generate the same name for mulitple network devices (so some will revert to the "ethX" names). With this patch, device naming code checks if ARI is enabled for a PCI network device, and uses the full 8-bit function number for naming to avoid this situation. This should improve readability and predictability of device names. Here is an example of how this change would affect naming: before patch | after patch ----------------------------- ens2f0 | ens2f0 NPAR partition 0 (in PCI slot 2) ens2f1 | ens2f1 NPAR partition 1 ... ens2f7 | ens2f7 NPAR partition 7 eth1 | ens2f8 NPAR partition 8 eth2 | ens2f9 NPAR partition 9
Diffstat (limited to 'NEWS')
0 files changed, 0 insertions, 0 deletions