> -Original Message-
> From: Lennart Poettering
> Sent: Monday, January 13, 2020 4:18 AM
> To: Haiyang Zhang
> Cc: Stephen Hemminger ; systemd-
> de...@lists.freedesktop.org; Michael Kelley
> Subject: Re: [systemd-devel] Better network naming on Hyper-V/Azure?
&g
On Fr, 10.01.20 16:17, Haiyang Zhang (haiya...@microsoft.com) wrote:
> > My guess is that this is a lot like SR-IOV slot number that we can
> > already use to name interfaces, right? If so, supporting things the
> > same way sounds totally OK.
>
> Thanks for your explanation. We do want to use the
> -Original Message-
> From: Lennart Poettering
> Sent: Friday, January 10, 2020 10:55 AM
> To: Haiyang Zhang
> Cc: Stephen Hemminger ; systemd-
> de...@lists.freedesktop.org; Michael Kelley
> Subject: Re: [systemd-devel] Better network naming on Hyper-V/Azure?
On Fr, 10.01.20 15:37, Haiyang Zhang (haiya...@microsoft.com) wrote:
> > 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 enabl
> -Original Message-
> From: Haiyang Zhang
> Sent: Tuesday, January 7, 2020 11:01 AM
> To: Lennart Poettering ; Stephen Hemminger
>
> Cc: systemd-devel@lists.freedesktop.org; Michael Kelley
>
> Subject: RE: [systemd-devel] Better network naming on Hyper-V/
On Tue, 7 Jan 2020 19:11:19 +0100
Lennart Poettering wrote:
> On Di, 07.01.20 09:53, Stephen Hemminger (step...@networkplumber.org) wrote:
>
> > On Tue, 7 Jan 2020 15:01:25 +0100
> > Lennart Poettering wrote:
> >
> > > On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org)
> >
On Di, 07.01.20 09:53, Stephen Hemminger (step...@networkplumber.org) wrote:
> On Tue, 7 Jan 2020 15:01:25 +0100
> Lennart Poettering wrote:
>
> > On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
> >
> > > About a year ago there was some discussion on having persistent
On Tue, 7 Jan 2020 15:01:25 +0100
Lennart Poettering wrote:
> On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
>
> > About a year ago there was some discussion on having persistent network
> > names
> > on Hyper-V/Azure. Haiyang did some patches to add an attribute w
On Di, 07.01.20 16:01, Haiyang Zhang (haiya...@microsoft.com) wrote:
> > I have no idea what that means, what is Accelerated Networking?
>
> On Azure, "Accelerated Networking" means SRIOV / VF NICs.
There's nowadays already support for SR-IOV naming in place:
https://www.freedesktop.org/software
(resending after subscribed to systemd-devel)
> -Original Message-
> From: Lennart Poettering
> Sent: Tuesday, January 7, 2020 9:01 AM
> To: Stephen Hemminger
> Cc: systemd-devel@lists.freedesktop.org; Haiyang Zhang
>
> Subject: Re: [systemd-devel] Better netw
On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
> About a year ago there was some discussion on having persistent network names
> on Hyper-V/Azure. Haiyang did some patches to add an attribute which
> could be used by udev to do this. But there are some reluctance beca
About a year ago there was some discussion on having persistent network names
on Hyper-V/Azure. Haiyang did some patches to add an attribute which
could be used by udev to do this. But there are some reluctance because
of how the channel id works.
The motivation to provide network naming is to all
12 matches
Mail list logo
