67 lines
2.9 KiB
Diff
67 lines
2.9 KiB
Diff
From b5e3ca17a2cee98d0fdae4cee0f285a9052c908c Mon Sep 17 00:00:00 2001
|
|
From: Franck Bui <fbui@suse.com>
|
|
Date: Mon, 10 Oct 2022 16:31:39 +0200
|
|
Subject: [PATCH 1012/1012] man: describe the net naming schemes specific to
|
|
SLE
|
|
|
|
Fixes: bsc#1204179
|
|
---
|
|
man/systemd.net-naming-scheme.xml | 42 +++++++++++++++++++++++++++++++
|
|
1 file changed, 42 insertions(+)
|
|
|
|
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
|
|
index 6c14810a3e..9b94eff52e 100644
|
|
--- a/man/systemd.net-naming-scheme.xml
|
|
+++ b/man/systemd.net-naming-scheme.xml
|
|
@@ -395,6 +395,48 @@
|
|
particular version of systemd).</para>
|
|
</refsect1>
|
|
|
|
+ <refsect1>
|
|
+ <title>SLE History</title>
|
|
+
|
|
+ <para>Additionally, the following "naming schemes" have also been defined on SLE products:</para>
|
|
+
|
|
+ <variablelist>
|
|
+ <varlistentry>
|
|
+ <term><constant>sle15-sp3</constant></term>
|
|
+
|
|
+ <listitem><para>This naming scheme is available since <varname>SLE15-SP3</varname> and is based on
|
|
+ the <constant>v238</constant> naming scheme described previously but also includes the following
|
|
+ changes.</para>
|
|
+
|
|
+ <para>When a PCI slot is associated with a PCI bridge that has multiple child network
|
|
+ controllers, the same value of the <varname>ID_NET_NAME_SLOT</varname> property might be derived
|
|
+ for those controllers. This would cause a naming conflict if the property is selected as the device
|
|
+ name. Now, we detect this situation and don't produce the <varname>ID_NET_NAME_SLOT</varname>
|
|
+ property.</para></listitem>
|
|
+ </varlistentry>
|
|
+
|
|
+ <varlistentry>
|
|
+ <term><constant>sle15-sp4</constant></term>
|
|
+
|
|
+ <listitem><para>Available since <varname>SLE15-SP4</varname> and is based on the
|
|
+ <constant>sle15-sp3</constant> naming scheme described previously but also includes the following
|
|
+ change.</para>
|
|
+
|
|
+ <para>PCI hotplug slot names for the s390 PCI driver are a hexadecimal representation
|
|
+ of the <filename>function_id</filename> device attribute. This attribute is now used to build the
|
|
+ <varname>ID_NET_NAME_SLOT</varname>. Before that, all slot names were parsed as decimal
|
|
+ numbers, which could either result in an incorrect value of the <varname>ID_NET_NAME_SLOT</varname>
|
|
+ property or none at all.</para>
|
|
+
|
|
+ <para>Some firmware and hypervisor implementations report unreasonable high numbers for the onboard
|
|
+ index. To prevent the generation of bogus onbard interface names, index numbers greater than 16381
|
|
+ (2^14-1) were ignored. For s390 PCI devices index values up to 65535 (2^16-1) are valid. To account
|
|
+ for that, the limit is increased to now 65535.</para></listitem>
|
|
+ </varlistentry>
|
|
+
|
|
+ </variablelist>
|
|
+ </refsect1>
|
|
+
|
|
<refsect1>
|
|
<title>Examples</title>
|
|
|
|
--
|
|
2.35.3
|
|
|