From: Cong Wang <amwang@redhat.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>,
Adam Baker <linux@baker-net.org.uk>
Subject: Re: [Patch net-next 2/3] bridge: only expire the mdb entry when query is received
Date: Tue, 30 Apr 2013 11:32:04 +0800 [thread overview]
Message-ID: <1367292724.3216.6.camel@cr0> (raw)
In-Reply-To: <20130430032221.GA20471@gondor.apana.org.au>
On Tue, 2013-04-30 at 11:22 +0800, Herbert Xu wrote:
> On Tue, Apr 30, 2013 at 11:17:37AM +0800, Cong Wang wrote:
> >
> > One problem with this solution is that the temp mdb entry will no longer
> > be expired automatically any more, since no query no timer.
> >
> > I am wondering if we should find other way to fix it, for example,
> > touching the timer as long as there is multicast traffic (non-IGMP).
>
> mdb entries represent group subscriptions. So what you're saying
> is that group subscriptions aren't expiring.
>
> Which isn't a problem at all since if there is no querier then group
> subscriptions shouldn't expire. There has to be at least one querier
> in the network for this thing to work. Otherwise it just degenerates
> into a non-snooping switch, which is OK.
Makes sense. I will put this in the changelog.
Thanks.
next prev parent reply other threads:[~2013-04-30 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 7:26 [Patch net-next 1/3] bridge: use the bridge IP addr as source addr of querier Cong Wang
2013-04-29 7:26 ` [Patch net-next 2/3] bridge: only expire the mdb entry when query is received Cong Wang
2013-04-30 3:17 ` Cong Wang
2013-04-30 3:22 ` Herbert Xu
2013-04-30 3:32 ` Cong Wang [this message]
2013-04-29 7:26 ` [Patch net-next 3/3] bridge: send query as soon as leave " Cong Wang
2013-04-29 7:43 ` Herbert Xu
2013-04-29 8:15 ` Cong Wang
2013-04-29 7:43 ` [Patch net-next 1/3] bridge: use the bridge IP addr as source addr of querier Herbert Xu
2013-04-29 8:17 ` Cong Wang
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=1367292724.3216.6.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux@baker-net.org.uk \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.