Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754072AbaGUJBo (ORCPT ); Mon, 21 Jul 2014 05:01:44 -0400 Received: from a.ns.miles-group.at ([95.130.255.143]:65276 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753857AbaGUJBm (ORCPT ); Mon, 21 Jul 2014 05:01:42 -0400 Message-ID: <53CCD6F2.6020909@nod.at> Date: Mon, 21 Jul 2014 11:01:38 +0200 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Yue Zhang (OSTC DEV)" CC: "netdev@vger.kernel.org" , "driverdev-devel@linuxdriverproject.org" , LKML , Greg KH , "olaf@aepfle.de" , "jasowang@redhat.com" , "David S. Miller" , Haiyang Zhang , KY Srinivasan , Thomas Shao , Dexuan Cui Subject: Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation References: <1405680903-28176-1-git-send-email-yuezha@microsoft.com> <53CCB944.8090709@nod.at> <53CCCCAD.7080906@nod.at> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Yue, Am 21.07.2014 10:44, schrieb Yue Zhang (OSTC DEV): > Hi, Richard > > IMHO, all networking implementations should handle the cable offline event. Consider > this situation. I unplugged the network cable and connect it to a new network switch > after 10 seconds. If the DHCP renew is not triggered, the network will break. I think in > normal cases, it should already been handled properly. Unless there is a strong > justification for not doing this. In that case, we shouldn't renew DHCP anyway. I agree that they should handle the cable offline event. My concern is that 10 seconds is maybe not a the right choice. (As we cannot know all implementations) Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/