From: David Miller <davem@davemloft.net>
To: fleitner@redhat.com
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
fubar@us.ibm.com, andy@greyhouse.net
Subject: Re: [PATCH 2/3] bonding: fix to rejoin multicast groups immediately
Date: Tue, 05 Oct 2010 20:28:53 -0700 (PDT) [thread overview]
Message-ID: <20101005.202853.39191290.davem@davemloft.net> (raw)
In-Reply-To: <1286324639-22314-2-git-send-email-fleitner@redhat.com>
From: Flavio Leitner <fleitner@redhat.com>
Date: Tue, 5 Oct 2010 21:23:58 -0300
> The IGMP specs states that if the system receives a
> membership report, it shouldn't send another for the
> next minute. However, if a link failure happens right
> after that, the backup slave and the switch connected
> to this slave will not know about the multicast and
> the traffic will hang for about a minute.
>
> This patch fixes it to rejoin multicast groups immediately
> after a failover restoring the multicast traffic.
>
> Signed-off-by: Flavio Leitner <fleitner@redhat.com>
Much better commit message :-)
Applied to net-next-2.6
next prev parent reply other threads:[~2010-10-06 3:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 7:12 [PATCH] bonding: rejoin multicast groups on VLANs Flavio Leitner
2010-09-29 13:17 ` Flavio Leitner
2010-09-30 20:45 ` [PATCH v2] " Flavio Leitner
2010-10-04 13:24 ` Andy Gospodarek
2010-10-05 22:07 ` Flavio Leitner
2010-10-06 0:23 ` [PATCH 1/3] " Flavio Leitner
2010-10-06 3:28 ` David Miller
2010-10-06 12:12 ` Andy Gospodarek
2010-10-06 0:23 ` [PATCH 2/3] bonding: fix to rejoin multicast groups immediately Flavio Leitner
2010-10-06 3:28 ` David Miller [this message]
2010-10-06 0:23 ` [PATCH 3/3] bonding: add retransmit membership reports tunable Flavio Leitner
2010-10-06 3:29 ` David Miller
2010-09-30 20:46 ` [PATCH] " Flavio Leitner
2010-09-29 18:44 ` [PATCH] bonding: rejoin multicast groups on VLANs Andy Gospodarek
2010-09-29 19:35 ` Flavio Leitner
2010-09-29 19:54 ` Andy Gospodarek
2010-09-29 20:38 ` Flavio Leitner
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=20101005.202853.39191290.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fleitner@redhat.com \
--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).