netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Brian Haley <brian.haley@hp.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	David Miller <davem@davemloft.net>,
	YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
	Simon Horman <horms@verge.net.au>,
	Alex Sidorenko <alexandre.sidorenko@hp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] bonding: send IPv6 neighbor advertisement on failover
Date: Fri, 10 Oct 2008 11:27:05 -0400	[thread overview]
Message-ID: <48EF7449.4020508@hp.com> (raw)
In-Reply-To: <48EEA752.6030505@hp.com>

Brian Haley wrote:
> Updated to address Vlad's comment about storing the link-local IPv6
> address in the bond/vlan structure, I no longer overwrite the existing
> address with a newer one.  Also added missed locking for the inet6_dev.
> 
> I don't see any way to address David Steven's comment since there is
> currently no NA tunable in the IPv6 code.
> 
> ---
> 
> This patch adds better IPv6 failover support for bonding devices,
> especially when in active-backup mode and there are only IPv6 addresses
> configured, as reported by Alex Sidorenko.
> 
> - Creates a new file, net/drivers/bonding/bond_ipv6.c, for the
>   IPv6-specific routines.  Both regular bonds and VLANs over bonds
>   are supported.
> 
> - Adds a new tunable, num_unsol_na, to limit the number of unsolicited
>   IPv6 Neighbor Advertisements that are sent on a failover event.
>   Default is 1.
> 
> - Creates two new IPv6 neighbor discovery functions:
> 
>   ndisc_build_skb()
>   ndisc_send_skb()
> 
>   These were required to support VLANs since we have to be able to
>   add the VLAN id to the skb since ndisc_send_na() and friends
>   shouldn't be asked to do this.  These two routines are basically
>   __ndisc_send() split into two pieces, in a slightly different order.
> 
> - Updates Documentation/networking/bonding.txt and bumps the rev of bond
>   support to 3.4.0.
> 
> On failover, this new code will generate one packet:
> 
> - An unsolicited IPv6 Neighbor Advertisement, which helps the switch
>   learn that the address has moved to the new slave.
> 
> Testing has shown that sending just the NA results in pretty good
> behavior when in active-back mode, I saw no lost ping packets for example.
> 
> -Brian
> 
> Signed-off-by: Brian Haley <brian.haley@hp.com>
> ---
> 

Looks good to me.  This provides a nice base that we can build on.

-vlad

  parent reply	other threads:[~2008-10-10 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  0:52 [PATCH v2] bonding: send IPv6 neighbor advertisement on failover Brian Haley
2008-10-10  2:23 ` David Stevens
2008-10-10 14:34   ` Brian Haley
2008-10-10 15:03     ` David Stevens
2008-10-10 15:53       ` Jay Vosburgh
2008-10-10 16:04         ` Brian Haley
2008-10-10 16:29           ` Vlad Yasevich
2008-10-10 16:56             ` Sridhar Samudrala
2008-10-10 17:15               ` Vlad Yasevich
2008-10-10 15:27 ` Vlad Yasevich [this message]
2008-10-27 20:07 ` Brian Haley
2008-10-28  0:24   ` Jay Vosburgh

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=48EF7449.4020508@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=alexandre.sidorenko@hp.com \
    --cc=brian.haley@hp.com \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=horms@verge.net.au \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).