shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man/net-naming-scheme: mention that NAMING_BRIDGE_MULTIFUNCTION_SLOT is reverted

Browse Source 
Follow-up for af7417ac7b.
Closes #33596.

(cherry picked from commit 1c0130e8dc)
This commit is contained in:
Yu Watanabe 2024-08-02 16:45:15 +09:00 committed by Luca Boccassi
parent ab4e1faca6
commit ce940b62ac
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
man/systemd.net-naming-scheme.xml
View File

@ -478,7 +478,8 @@
bridge as that would create naming conflict when there are more child devices on that bridge. Now, 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 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 PCI device has multiple functions. This is safe because distinct function number is a part of
the device name for multifunction devices.</para> the device name for multifunction devices. Note, this is reverted in <constant>v255</constant>.
See below.</para>
<xi:include href="version-info.xml" xpointer="v251"/> <xi:include href="version-info.xml" xpointer="v251"/>
</listitem> </listitem>
@ -521,6 +522,9 @@
<listitem><para>Naming was changed for SR-IOV virtual device representors to enable the <listitem><para>Naming was changed for SR-IOV virtual device representors to enable the
change introduced in <constant>v254</constant> by default.</para> change introduced in <constant>v254</constant> by default.</para>
<para>If we detect that a PCI device associated with a slot is a PCI bridge, we no longer set
<varname>ID_NET_NAME_SLOT</varname>, reverting a change that was introduced in v251.</para>
<xi:include href="version-info.xml" xpointer="v255"/> <xi:include href="version-info.xml" xpointer="v255"/>
</listitem> </listitem>
</varlistentry> </varlistentry>