From: Brian Haley <brian.haley@hp.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Alex Sidorenko <alexandre.sidorenko@hp.com>,
David Miller <davem@davemloft.net>,
fubar@linux.vnet.ibm.com, Simon Horman <horms@verge.net.au>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netdev-owner@vger.kernel.org,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH v2] bonding: send IPv6 neighbor advertisement on failover
Date: Fri, 10 Oct 2008 10:34:58 -0400 [thread overview]
Message-ID: <48EF6812.2090600@hp.com> (raw)
In-Reply-To: <OFDFB5153E.E37AC842-ON882574DE.000CEB50-882574DE.000D286A@us.ibm.com>
David Stevens wrote:
>> I don't see any way to address David Steven's comment since there is
>> currently no NA tunable in the IPv6 code.
>
> Brian,
> How do you feel about doubling up with dad_transmits for that
> part?
I don't really want to since this is bonding-specific behavior, and
we're not performing DAD for the address. This is just another sysfs
entry: /sys/class/net/bond*/bonding/num_unsol_na, not a sysctl.
> At least the switch/cache updating portion is the same
> in both cases.
I don't think they are. In the DAD case we're probing for another node
that might have the address configured, in the bond failover case we
want to update the switch quickly so we don't drop packets.
-Brian
next prev parent reply other threads:[~2008-10-10 14:35 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 [this message]
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
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=48EF6812.2090600@hp.com \
--to=brian.haley@hp.com \
--cc=alexandre.sidorenko@hp.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=fubar@linux.vnet.ibm.com \
--cc=horms@verge.net.au \
--cc=netdev-owner@vger.kernel.org \
--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).