From: David Miller <davem@davemloft.net>
To: linus.luessing@web.de
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
stephen@networkplumber.org, linux-kernel@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH net-next 0/4] bridge: multicast snooping exports #2
Date: Tue, 08 Jul 2014 16:13:41 -0700 (PDT) [thread overview]
Message-ID: <20140708.161341.103939871003850198.davem@davemloft.net> (raw)
In-Reply-To: <1404704477-19448-1-git-send-email-linus.luessing@web.de>
From: Linus Lüssing <linus.luessing@web.de>
Date: Mon, 7 Jul 2014 05:41:15 +0200
"0/4"? Surely you meant "0/2" :-)
> Some people pointed out to me that it might be helpful to add stubs for
> the newly added multicast exports. That way e.g. batman-adv should continue
> to be compile and useable without having to have a kernel compiled
> with bridge code in the future. This is what the first patch is supposed
> to do.
>
> The second patch adds a third multicast export for the bridge which
> e.g. batman-adv is supposed to use, too, soon: Just like the bridge
> disables its multicast snooping activities if no querier is present,
> batman-adv needs to do the same if bridges are involved.
>
>
> These three exports should be the final ones needed to marry the bridge
> multicast snooping with the batman-adv multicast optimizations recently
> added for the 3.15 kernel, allowing to use these optimzations in common
> setups having a bridge on top of e.g. bat0, too. So far these bridged
> setups would fall back to simple flooding through the batman-adv mesh
> network for any multicast packet entering bat0.
>
> More information about the batman-adv multicast optimizations currently
> implemented can be found here:
>
> http://www.open-mesh.org/projects/batman-adv/wiki/Basic-multicast-optimizations
>
> The integration on the batman-adv side could afterwards look like this,
> for instance (now including the third export):
>
> http://git.open-mesh.org/batman-adv.git/commitdiff/61e4f6af4b7a21ed4040f2e711d50c778e5b6d93?hp=6ae4281474675fbca5bedcf768972a32db586eb6
Series applied, thanks.
prev parent reply other threads:[~2014-07-08 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 3:41 Linus Lüssing
2014-07-07 3:41 ` [PATCH net-next 1/2] bridge: adding stubs for multicast exports Linus Lüssing
2014-07-08 18:41 ` Cong Wang
2014-07-07 3:41 ` [PATCH net-next 2/2] bridge: export knowledge about the presence of IGMP/MLD queriers Linus Lüssing
2014-07-08 23:13 ` David Miller [this message]
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=20140708.161341.103939871003850198.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bridge@lists.linux-foundation.org \
--cc=linus.luessing@web.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®