From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: haiyangz@microsoft.com, netdev@vger.kernel.org, sthemmin@microsoft.com
Subject: Re: [PATCH net-next] hv_netvsc: propogate Hyper-V friendly name into interface alias
Date: Wed, 18 Apr 2018 21:20:02 -0400 (EDT) [thread overview]
Message-ID: <20180418.212002.370060356228679393.davem@davemloft.net> (raw)
In-Reply-To: <20180417212530.6997-1-sthemmin@microsoft.com>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 17 Apr 2018 14:25:30 -0700
> This patch implement the 'Device Naming' feature of the Hyper-V
> network device API. In Hyper-V on the host through the GUI or PowerShell
> it is possible to enable the device naming feature which causes
> the host to make available to the guest the name of the device.
> This shows up in the RNDIS protocol as the friendly name.
>
> The name has no particular meaning and is limited to 256 characters.
> The value can only be set via PowerShell on the host, but could
> be scripted for mass deployments. The default value is the
> string 'Network Adapter' and since that is the same for all devices
> and useless, the driver ignores it.
>
> In Windows, the value goes into a registry key for use in SNMP
> ifAlias. For Linux, this patch puts the value in the network
> device alias property; where it is visible in ip tools and SNMP.
>
> The host provided ifAlias is just a suggestion, and can be
> overridden by later ip commands.
>
> Also requires exporting dev_set_alias in netdev core.
>
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
This looks fine, applied, thanks.
prev parent reply other threads:[~2018-04-19 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:25 [PATCH net-next] hv_netvsc: propogate Hyper-V friendly name into interface alias Stephen Hemminger
2018-04-19 1:20 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180418.212002.370060356228679393.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox