arp_notify: allow drivers to explicitly request a notification event.
Currently such notifications are only generated when the device comes up or the address changes. However one use case for these notifications is to enable faster network recovery after a virtual machine migration (by causing switches to relearn their MAC tables). A migration appears to the network stack as a temporary loss of carrier and therefore does not trigger either of the current conditions. Rather than adding carrier up as a trigger (which can cause issues when interfaces a flapping) simply add an interface which the driver can use to explicitly trigger the notification. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Stephen Hemminger <shemminger@linux-foundation.org> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: David S. Miller <davem@davemloft.net> Cc: netdev@vger.kernel.org Cc: stable@kernel.org Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
3f8dc2362f
commit
06c4648d46
4 changed files with 22 additions and 0 deletions
|
@ -1772,6 +1772,8 @@ extern void netif_carrier_on(struct net_device *dev);
|
|||
|
||||
extern void netif_carrier_off(struct net_device *dev);
|
||||
|
||||
extern void netif_notify_peers(struct net_device *dev);
|
||||
|
||||
/**
|
||||
* netif_dormant_on - mark device as dormant.
|
||||
* @dev: network device
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue