diff options
| author | Michal Sekletar <msekleta@redhat.com> | 2022-03-23 17:34:12 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-04-06 11:51:03 +0200 |
| commit | 66425daf2c68793adf24a48a26d58add8662e83f (patch) | |
| tree | 435ad2e826c0bcf96b80ba58729268f8365873c5 /man/systemd.net-naming-scheme.xml | |
| parent | f7ad16287960fa600d1c5cdfd4dc23ff2179a96d (diff) | |
| download | systemd-66425daf2c68793adf24a48a26d58add8662e83f.tar.gz | |
udev/net_id: avoid slot based names only for single function devices
If we have two or more devices that share the same slot but they are
also multifunction then it is OK to use the slot information even if it
is the same for all of them. Name conflict will be avoided because we
will append function number and form names like, ens1f1, ens1f2...
Diffstat (limited to 'man/systemd.net-naming-scheme.xml')
| -rw-r--r-- | man/systemd.net-naming-scheme.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml index 41408411fc..e5a3d7a313 100644 --- a/man/systemd.net-naming-scheme.xml +++ b/man/systemd.net-naming-scheme.xml @@ -403,6 +403,18 @@ </listitem> </varlistentry> + <varlistentry> + <term><constant>v251</constant></term> + + <listitem><para>Since version <constant>v247</constant> we no longer set + <varname>ID_NET_NAME_SLOT</varname> 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.</para> + </listitem> + </varlistentry> + </variablelist> <para>Note that <constant>latest</constant> may be used to denote the latest scheme known (to this |