• B
    ipv4, ipv6, bonding: Restore control over number of peer notifications · ad246c99
    Ben Hutchings 提交于
    For backward compatibility, we should retain the module parameters and
    sysfs attributes to control the number of peer notifications
    (gratuitous ARPs and unsolicited NAs) sent after bonding failover.
    Also, it is possible for failover to take place even though the new
    active slave does not have link up, and in that case the peer
    notification should be deferred until it does.
    
    Change ipv4 and ipv6 so they do not automatically send peer
    notifications on bonding failover.
    
    Change the bonding driver to send separate NETDEV_NOTIFY_PEERS
    notifications when the link is up, as many times as requested.  Since
    it does not directly control which protocols send notifications, make
    num_grat_arp and num_unsol_na aliases for a single parameter.  Bump
    the bonding version number and update its documentation.
    Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
    Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
    Acked-by: NBrian Haley <brian.haley@hp.com>
    Signed-off-by: NDavid S. Miller <davem@davemloft.net>
    ad246c99
bond_main.c 132.2 KB