From: Richard Weinberger <richard@nod.at>
To: "Yue Zhang (OSTC DEV)" <yuezha@microsoft.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Haiyang Zhang <haiyangz@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Thomas Shao <huishao@microsoft.com>,
Dexuan Cui <decui@microsoft.com>
Subject: Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation
Date: Mon, 21 Jul 2014 11:01:38 +0200 [thread overview]
Message-ID: <53CCD6F2.6020909@nod.at> (raw)
In-Reply-To: <DC7803B42427924284F2D5252E076A3B4476A479@SINEX14MBXC416.southpacific.corp.microsoft.com>
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
next prev parent reply other threads:[~2014-07-21 9:01 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:55 [PATCH] Hyperv: Trigger DHCP renew after host hibernation Yue Zhang
2014-07-18 10:55 ` Yue Zhang
2014-07-18 10:13 ` Varka Bhadram
2014-07-18 10:13 ` Varka Bhadram
2014-07-21 2:45 ` Yue Zhang (OSTC DEV)
2014-07-21 2:45 ` Yue Zhang (OSTC DEV)
2014-07-18 13:40 ` Richard Weinberger
2014-07-18 13:40 ` Richard Weinberger
2014-07-21 2:44 ` Yue Zhang (OSTC DEV)
2014-07-21 2:44 ` Yue Zhang (OSTC DEV)
2014-07-21 6:55 ` Richard Weinberger
2014-07-21 6:55 ` Richard Weinberger
2014-07-21 8:05 ` Yue Zhang (OSTC DEV)
2014-07-21 8:05 ` Yue Zhang (OSTC DEV)
2014-07-21 8:17 ` Richard Weinberger
2014-07-21 8:17 ` Richard Weinberger
2014-07-21 8:44 ` Yue Zhang (OSTC DEV)
2014-07-21 8:44 ` Yue Zhang (OSTC DEV)
2014-07-21 9:01 ` Richard Weinberger [this message]
2014-07-21 9:18 ` Olaf Hering
2014-07-21 21:32 ` David Miller
2014-07-21 21:32 ` David Miller
2014-08-07 22:37 ` Richard Weinberger
2014-08-07 22:37 ` Richard Weinberger
2014-08-08 3:13 ` Dexuan Cui
2014-08-08 3:13 ` Dexuan Cui
2014-08-08 3:32 ` Greg KH
2014-08-08 3:32 ` Greg KH
2014-08-08 8:11 ` Dexuan Cui
2014-08-08 8:11 ` Dexuan Cui
2014-08-08 13:45 ` Greg KH
2014-08-08 13:45 ` Greg KH
2014-08-08 16:28 ` Stephen Hemminger
2014-08-11 3:23 ` Dexuan Cui
2014-08-11 3:51 ` Florian Fainelli
2014-08-11 4:22 ` Bill Fink
2014-08-11 4:22 ` Bill Fink
2014-08-12 7:51 ` Dexuan Cui
2014-08-12 7:51 ` Dexuan Cui
2014-08-12 7:48 ` Dexuan Cui
2014-08-12 7:48 ` Dexuan Cui
2014-08-11 10:45 ` Tom Gundersen
2014-08-11 10:45 ` Tom Gundersen
2014-08-12 8:29 ` Dexuan Cui
2014-08-12 8:29 ` Dexuan Cui
2014-08-13 13:15 ` Tom Gundersen
2014-08-13 13:15 ` Tom Gundersen
2014-08-13 13:34 ` Dan Williams
2014-08-13 13:34 ` Dan Williams
2014-08-14 5:19 ` Dexuan Cui
2014-08-14 5:19 ` Dexuan Cui
2014-08-11 3:29 ` Dexuan Cui
2014-08-11 3:29 ` Dexuan Cui
2014-07-21 9:42 ` Tom Gundersen
2014-07-21 10:21 ` Yue Zhang (OSTC DEV)
2014-07-21 10:21 ` Yue Zhang (OSTC DEV)
2014-07-21 13:11 ` Lennart Poettering
2014-07-21 13:11 ` Lennart Poettering
2014-07-21 17:17 ` Dan Williams
2014-07-21 17:17 ` Dan Williams
2014-07-21 14:06 ` Tom Gundersen
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=53CCD6F2.6020909@nod.at \
--to=richard@nod.at \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=huishao@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=yuezha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.