From: Ben Hutchings <bhutchings@solarflare.com>
To: Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org, Ian Campbell <Ian.Campbell@citrix.com>
Subject: [PATCH net-next-2.6 0/3] bonding,ipv4,ipv6,vlan: Use notifiers to trigger advertisements on failover
Date: Sat, 16 Apr 2011 00:41:01 +0100 [thread overview]
Message-ID: <1302910861.2845.36.camel@bwh-desktop> (raw)
It is undesirable for the bonding driver to be poking into higher
level protocols, and notifiers provide a way to avoid that.
Ian added NETDEV_NOTIFY_PEERS to trigger gratuitous ARP on VM migration.
We should extend that to unsolicited NAs and propagate it through VLANs,
then treat bonding failover in the same way.
Ben.
Ben Hutchings (3):
ipv6: Send unsolicited neighbour advertisements when notified
vlan: Propagate NETDEV_NOTIFY_PEERS notifier
bonding,ipv4,ipv6,vlan: Handle NETDEV_BONDING_FAILOVER like
NETDEV_NOTIFY_PEERS
drivers/net/bonding/Makefile | 3 -
drivers/net/bonding/bond_ipv6.c | 225 --------------------------------------
drivers/net/bonding/bond_main.c | 96 ----------------
drivers/net/bonding/bond_sysfs.c | 80 --------------
drivers/net/bonding/bonding.h | 29 -----
net/8021q/vlan.c | 12 ++
net/ipv4/devinet.c | 1 +
net/ipv6/ndisc.c | 27 +++++
8 files changed, 40 insertions(+), 433 deletions(-)
delete mode 100644 drivers/net/bonding/bond_ipv6.c
--
1.7.4
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next reply other threads:[~2011-04-15 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 23:41 Ben Hutchings [this message]
2011-04-18 6:34 ` [PATCH net-next-2.6 0/3] bonding,ipv4,ipv6,vlan: Use notifiers to trigger advertisements on failover David Miller
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=1302910861.2845.36.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=Ian.Campbell@citrix.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox