From: Haiyang Zhang <haiyangz@microsoft.com>
Date: Tue, 9 Feb 2016 15:31:34 +0000
1) I share your concern as well. Is there a universal way to immediately trigger
DHCP renew of all current and future daemons with a single event from kernel?
If not, can we put the delay (RNDIS_STATUS_NETWORK_CHANGE only) into a
tunable variable of this driver?
2) We used to have the call_usermodehelper "/etc/init.d/network restart" to
trigger DHCP renew. In commit 27a70af3f4, Vitaly has replaced it with the current
code that updates the link status with at least 2 seconds interval, so that the
"link_watch infrastructure" can send notification out. link_watch infrastructure
only sends one notification per second.
If the daemon is waiting for the link state change properly, there should be
no delay necessary at all.