From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller 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) Message-ID: <20180418.212002.370060356228679393.davem@davemloft.net> References: <20180417212530.6997-1-sthemmin@microsoft.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: haiyangz@microsoft.com, netdev@vger.kernel.org, sthemmin@microsoft.com To: stephen@networkplumber.org Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:51186 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752135AbeDSBUD (ORCPT ); Wed, 18 Apr 2018 21:20:03 -0400 In-Reply-To: <20180417212530.6997-1-sthemmin@microsoft.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Stephen Hemminger 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 This looks fine, applied, thanks.