bonding, ipv4, ipv6, vlan: Handle NETDEV_BONDING_FAILOVER like NETDEV_NOTIFY_PEERS
It is undesirable for the bonding driver to be poking into higher level protocols, and notifiers provide a way to avoid that. This does mean removing the ability to configure reptitition of gratuitous ARPs and unsolicited NAs. Signed-off-by:Ben Hutchings <bhutchings@solarflare.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- drivers/net/bonding/Makefile 0 additions, 3 deletionsdrivers/net/bonding/Makefile
- drivers/net/bonding/bond_main.c 0 additions, 94 deletionsdrivers/net/bonding/bond_main.c
- drivers/net/bonding/bond_sysfs.c 0 additions, 80 deletionsdrivers/net/bonding/bond_sysfs.c
- drivers/net/bonding/bonding.h 0 additions, 29 deletionsdrivers/net/bonding/bonding.h
- net/8021q/vlan.c 2 additions, 1 deletionnet/8021q/vlan.c
- net/ipv4/devinet.c 1 addition, 0 deletionsnet/ipv4/devinet.c
- net/ipv6/ndisc.c 1 addition, 0 deletionsnet/ipv6/ndisc.c
Loading
Please register or sign in to comment