netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/3] bonding: Improve IGMP join processing
Date: Tue, 06 Mar 2007 14:55:28 -0500	[thread overview]
Message-ID: <45EDC730.40007@hp.com> (raw)
In-Reply-To: <20070301194305.GB3199@gospo.rdu.redhat.com>

Andy Gospodarek wrote:
> If we are easily able to differentiate between the multicast addresses
> in the mc_list as to which are for ipv4 and which are for ipv6 then it
> would be easy to call-out to something in the ipv6 mcast code when
> needed instead of always calling out to ipv4 code.

I've been unable to figure out exactly what you're referring to in the 
code (bond_main.c), it seems to failover all multicast addresses, 
regardless of what address family they are.  I might have missed 
something in 4K lines of code though?

-Brian

  parent reply	other threads:[~2007-03-06 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01  1:03 [PATCH 3/3] bonding: Improve IGMP join processing Jay Vosburgh
2007-03-01 16:49 ` Andy Gospodarek
2007-03-01 17:05   ` Jay Vosburgh
2007-03-01 19:25     ` Brian Haley
2007-03-01 19:43       ` Andy Gospodarek
2007-03-01 21:58         ` Jay Vosburgh
2007-03-06 19:55         ` Brian Haley [this message]
2007-03-06 20:39           ` Jay Vosburgh
2007-03-06 20:44             ` Andy Gospodarek
2007-03-06 22:32               ` David Stevens
2007-03-06 23:15                 ` [Bonding-devel] " Jay Vosburgh
2007-03-07  0:45                   ` David Stevens
2007-03-07  1:50                   ` Andy Gospodarek
2007-03-07  3:21                     ` David Stevens
2007-03-09 16:53                       ` Andy Gospodarek

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=45EDC730.40007@hp.com \
    --to=brian.haley@hp.com \
    --cc=andy@greyhouse.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=fubar@us.ibm.com \
    --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).