From 9fc363f03fb69db8bf25a6c854489d58eb11617e Mon Sep 17 00:00:00 2001 From: Lukas Nykryn Date: Fri, 9 Feb 2024 15:51:36 +0100 Subject: [PATCH] man: reorder the list of supported naming schemes Let's put the upstream version first, followed by the RHEL9 backports and move RHEL8 ones to separate section. rhel-only Related: RHEL-7026 --- man/systemd.net-naming-scheme.xml | 104 +++++++++++++----------------- 1 file changed, 46 insertions(+), 58 deletions(-) diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml index 532d6ddb15..a5903c6d04 100644 --- a/man/systemd.net-naming-scheme.xml +++ b/man/systemd.net-naming-scheme.xml @@ -460,26 +460,58 @@ - rhel-8.0 + rhel-9.0 - Naming was changed for virtual network interfaces created with SR-IOV and NPAR and - for devices where the PCI network controller device does not have a slot number associated. + Since version v247 we no longer set + ID_NET_NAME_SLOT if we detect that a PCI device associated with a slot is a PCI + bridge as that would create naming conflict when there are more child devices on that bridge. Now, + this is relaxed and we will use slot information to generate the name based on it but only if + the PCI device has multiple functions. This is safe because distinct function number is a part of + the device name for multifunction devices. + + - SR-IOV virtual devices are named based on the name of the parent interface, with a suffix of - vport, where port is the - virtual device number. Previously those virtual devices were named as if completely independent. - + + rhel-9.1 - The ninth and later NPAR virtual devices are named following the scheme used for the first - eight NPAR partitions. Previously those devices were not renamed and the kernel default - ("ethN") was used. + Same as naming scheme rhel-9.0. + - Names are also generated for PCI devices where the PCI network controller device does not - have an associated slot number itself, but one of its parents does. Previously those devices were - not renamed and the kernel default was used. + + rhel-9.2 + + Same as naming scheme rhel-9.0. + + + + rhel-9.3 + + Naming was changed for SR-IOV virtual device representors. + + The rslot suffix was added to differentiate SR-IOV + virtual device representors attached to a single physical device interface. + + + rhel-9.4 + + Same as naming scheme rhel-9.3. + + + + By default rhel-9.0 is used. + + RHEL-8 schemes + It is also possible to pick a scheme from RHEL-8 + + + rhel-8.0 + + Same as naming scheme v239. + + rhel-8.1 @@ -552,52 +584,8 @@ Same as naming scheme rhel-8.7. - - - rhel-9.0 - - Since version v247 we no longer set - ID_NET_NAME_SLOT if we detect that a PCI device associated with a slot is a PCI - bridge as that would create naming conflict when there are more child devices on that bridge. Now, - this is relaxed and we will use slot information to generate the name based on it but only if - the PCI device has multiple functions. This is safe because distinct function number is a part of - the device name for multifunction devices. - - - - - rhel-9.1 - - Same as naming scheme rhel-9.0. - - - - rhel-9.2 - - Same as naming scheme rhel-9.0. - - - - rhel-9.3 - - Naming was changed for SR-IOV virtual device representors. - - The rslot suffix was added to differentiate SR-IOV - virtual device representors attached to a single physical device interface. - - - - - - rhel-9.4 - - Same as naming scheme rhel-9.3. - - - - Note that latest may be used to denote the latest scheme known (to this - particular version of systemd). +