From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andy Gospodarek <andy@greyhouse.net>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, lhh@redhat.com, fubar@us.ibm.com,
bonding-devel@lists.sourceforge.net
Subject: Re: [net-2.6 PATCH] bonding: fix broken multicast with round-robin mode
Date: Wed, 31 Mar 2010 11:08:37 +0200 [thread overview]
Message-ID: <1270026517.2103.9.camel@edumazet-laptop> (raw)
In-Reply-To: <20100325214033.GA28741@gospo.rdu.redhat.com>
Le jeudi 25 mars 2010 à 17:40 -0400, Andy Gospodarek a écrit :
> Round-robin (mode 0) does nothing to ensure that any multicast traffic
> originally destined for the host will continue to arrive at the host when
> the link that sent the IGMP join or membership report goes down. One of
> the benefits of absolute round-robin transmit.
>
> Keeping track of subscribed multicast groups for each slave did not seem
> like a good use of resources, so I decided to simply send on the
> curr_active slave of the bond (typically the first enslaved device that
> is up). This makes failover management simple as IGMP membership
> reports only need to be sent when the curr_active_slave changes. I
> tested this patch and it appears to work as expected.
>
> Originally reported by Lon Hohberger <lhh@redhat.com>.
>
> Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
> CC: Lon Hohberger <lhh@redhat.com>
> CC: Jay Vosburgh <fubar@us.ibm.com>
>
> ---
> drivers/net/bonding/bond_main.c | 34 ++++++++++++++++++++++++++--------
> 1 files changed, 26 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index 430c022..0b38455 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -1235,6 +1235,11 @@ void bond_change_active_slave(struct bonding *bond, struct slave *new_active)
> write_lock_bh(&bond->curr_slave_lock);
> }
> }
> +
> + /* resend IGMP joins since all were sent on curr_active_slave */
> + if (bond->params.mode == BOND_MODE_ROUNDROBIN) {
> + bond_resend_igmp_join_requests(bond);
> + }
> }
>
> /**
> @@ -4138,22 +4143,35 @@ static int bond_xmit_roundrobin(struct sk_buff *skb, struct net_device *bond_dev
> struct bonding *bond = netdev_priv(bond_dev);
> struct slave *slave, *start_at;
> int i, slave_no, res = 1;
> + struct iphdr *iph = ip_hdr(skb);
>
> read_lock(&bond->lock);
>
> if (!BOND_IS_OK(bond))
> goto out;
> -
> /*
> - * Concurrent TX may collide on rr_tx_counter; we accept that
> - * as being rare enough not to justify using an atomic op here
> + * Start with the curr_active_slave that joined the bond as the
> + * default for sending IGMP traffic. For failover purposes one
> + * needs to maintain some consistency for the interface that will
> + * send the join/membership reports. The curr_active_slave found
> + * will send all of this type of traffic.
> */
> - slave_no = bond->rr_tx_counter++ % bond->slave_cnt;
> + if ((skb->protocol == htons(ETH_P_IP)) &&
> + (iph->protocol == htons(IPPROTO_IGMP))) {
Hmm...
iph->protocol is a u8, how can htons(IPPROTO_IGMP) be equal to
iph->protocol ?
[PATCH] bonding: bond_xmit_roundrobin() fix
Commit a2fd940f (bonding: fix broken multicast with round-robin mode)
added a problem on litle endian machines.
drivers/net/bonding/bond_main.c:4159: warning: comparison is always
false due to limited range of data type
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index 5b92fbf..5972a52 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -4156,7 +4156,7 @@ static int bond_xmit_roundrobin(struct sk_buff *skb, struct net_device *bond_dev
* send the join/membership reports. The curr_active_slave found
* will send all of this type of traffic.
*/
- if ((iph->protocol == htons(IPPROTO_IGMP)) &&
+ if ((iph->protocol == IPPROTO_IGMP) &&
(skb->protocol == htons(ETH_P_IP))) {
read_lock(&bond->curr_slave_lock);
next prev parent reply other threads:[~2010-03-31 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 21:40 [net-2.6 PATCH] bonding: fix broken multicast with round-robin mode Andy Gospodarek
2010-03-25 22:31 ` Jay Vosburgh
2010-03-26 0:49 ` [net-2.6 PATCH v2] " Andy Gospodarek
2010-03-26 0:55 ` Jay Vosburgh
2010-03-31 9:08 ` Eric Dumazet [this message]
2010-03-31 14:49 ` [net-2.6 PATCH] " Andy Gospodarek
2010-03-31 15:14 ` Eric Dumazet
2010-03-31 21:00 ` David Miller
2010-03-31 21:23 ` Eric Dumazet
2010-03-31 21:25 ` 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=1270026517.2103.9.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=andy@greyhouse.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=lhh@redhat.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