From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: fubar@us.ibm.com, andy@greyhouse.net, kaber@trash.net,
netdev@vger.kernel.org, brian.haley@hp.com
Subject: Re: [PATCH net-next-2.6] ipv4,ipv6,bonding: Restore control over number of peer notifications
Date: Fri, 29 Apr 2011 12:44:29 -0700 (PDT) [thread overview]
Message-ID: <20110429.124429.15250719.davem@davemloft.net> (raw)
In-Reply-To: <1303867552.2850.39.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 27 Apr 2011 02:25:52 +0100
> 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: Ben Hutchings <bhutchings@solarflare.com>
Applied, thanks.
prev parent reply other threads:[~2011-04-29 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 1:25 [PATCH net-next-2.6] ipv4,ipv6,bonding: Restore control over number of peer notifications Ben Hutchings
2011-04-27 1:44 ` Jay Vosburgh
2011-04-27 2:09 ` Brian Haley
2011-04-27 2:14 ` Ben Hutchings
2011-04-27 14:21 ` Brian Haley
2011-04-29 19:44 ` David Miller [this message]
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=20110429.124429.15250719.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=brian.haley@hp.com \
--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;
as well as URLs for NNTP newsgroup(s).