В Mon, 27 Jul 2015 18:29:57 +0000 "Keller, Jacob E" <jacob.e.kel...@intel.com> пишет:
> On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote: > > В Mon, 27 Jul 2015 17:52:59 +0000 > > "Keller, Jacob E" <jacob.e.kel...@intel.com> пишет: > > > > > Hello, > > > > > > I am working with a network device that can create virtual function > > > devices. When I create a large (>8) vfs for this device I get some > > > weird device names, > > > > > > If I create 64 vfs, I see something like: > > > > > > ens8 > > > ens8f[1-7] > > > ens8s[1-7] Are you sure? I do not see where such names would be generated. > > > enp8s[1-7]f[1-7] > > > > > > > All those names come directly from kernel. udev does not invent them > > - > > this is exactly what lspci shows. If it does not match lspci, you > > should provide more information. > > > > > ens8f1-64 or something? > > > > > > > Then kernel should enumerate them so; you really need to discuss it > > there. > > It looks like my issue comes from the "hotplug_slot" stuff, which > overwrites the "enp8s0f0" into "ens8"... that is what causes this dual > -name scheme confusion. > You can disable hotplug slot-based naming by setting suitable NamePolicy for network links (drop "slot"). _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
