> -----Original Message-----
> From: Haiyang Zhang
> Sent: Tuesday, January 7, 2020 11:01 AM
> To: Lennart Poettering <[email protected]>; Stephen Hemminger
> <[email protected]>
> Cc: [email protected]; Michael Kelley
> <[email protected]>
> Subject: RE: [systemd-devel] Better network naming on Hyper-V/Azure?
> Hyper-V offers netvsc devices (synthetic NICs) in the same sequence across
> reboots, so eth0 ... ethN names will associate to the same vNIC every time
> with Sync-probing currently.
>
> But if in the future, we enable Async-probing, the naming may not persistent
> across reboots. In my patch set (not yet upstream), I added a new attribute
> (dev_num) in sysfs to keep track of the device channel offer sequence. So user
> mode program can have the option to use this attribute to name NICs, and
> generates the same results for Async-probing as Sync-probing does.
Lennart and other systemd developers:
Could you also comment on my proposal above? It's to keep the naming results
of Async-probing same as that of sync-probing.
Thanks,
- Haiyang
_______________________________________________
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
