[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06b508cbb6b949f4b3e13e7797948e56@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
Date: Mon, 23 Jun 2014 12:47:52 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Olaf Hering <olaf@...fle.de>
CC: Greg KH <greg@...ah.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"driverdev-devel@...uxdriverproject.org"
<driverdev-devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [PATCH net-next] hyperv: Add handler for
RNDIS_STATUS_NETWORK_CHANGE event
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@...fle.de]
> Sent: Monday, June 23, 2014 4:03 AM
> To: Haiyang Zhang
> Cc: Greg KH; netdev@...r.kernel.org; jasowang@...hat.com; driverdev-
> devel@...uxdriverproject.org; linux-kernel@...r.kernel.org;
> davem@...emloft.net
> Subject: Re: [PATCH net-next] hyperv: Add handler for
> RNDIS_STATUS_NETWORK_CHANGE event
>
> On Fri, Jun 20, Haiyang Zhang wrote:
>
> > This command ("/etc/init.d/network restart") exists on our supported
> distros
> > currently. We will also look into some better ways to refresh the
> network for
> > the distros without this command. I have tried setting IF_OPER_DORMANT
> then
> > IF_OPER_UP, but not working. I will look into the suspend/resume cycle
> as
> > well.
>
> I think its reasonable to expect guest config changes on this new kind
> of host. Would a link-down/link-up event work? I'm sure it will, there
> is enough code floating around in the guests which handles cable unplug.
Do you mean netif_carrier_off() / netif_carrier_on()? They are already
called in the code before this patch, but DHCP renew is not triggered by
them.
Thanks,
- Haiyang
Powered by blists - more mailing lists