From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv5 0/3] batman-adv: Unicasting multicast reports to querier-node only
Date: Wed, 6 May 2015 21:38:57 +0200 [thread overview]
Message-ID: <20150506193856.GJ2423@odroid> (raw)
In-Reply-To: <1430940562-12148-1-git-send-email-linus.luessing@c0d3.blue>
PS: If you like the new compat solution better, then please let me
know what copyright header you'd like to have added.
Currently only compat-sources/net/ipv6/mcast_snoop.c has a header,
identical to the one in the upstream kernel. For the other files
I'm a little unsure about what to add. For instance
compat-sources/net/ipv4/igmp.c is a lot based on Herbert Xu's
work (similar to how mcast_snoop.c is based on Yoshifuji's work).
On Wed, May 06, 2015 at 09:29:19PM +0200, Linus Lüssing wrote:
> The last round of multicast patches send to the batman-adv mailinglist
> to add support for the multicast optimizations in bridged scenarios, too,
> unfortunately had one major conceptual flaw: It could lead to packet loss.
> It's not sufficient to have the unicasting of reports implemented on
> bridge-nodes only. Nodes without bridges need to treat reports the same
> way.
>
> The issue is described in detail here:
>
> https://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-listener-reports
>
>
> Cheers, Linus
>
> -----
>
> Changelog:
> v5:
> * Removed RFC tag: Needed exports got merged to net-next and are going to
> be available with Linux 4.2
> * Redid compat solution - now fully backwards compatible down to 2.6.33
> v4:
> * excluded bridge part from this patchset, they should
> hopefully be added to net-next soon
> * Added a compat solution (PATCH 3/3)
> * Removed Kconfig-depends as by David's suggestion the needed parsing
> functions for MLD are going to be forced built-ins even if IPv6 is
> going to be built as a module
> * Removed unused variable 'int ret' in batadv_mcast_is_report_ipv6()
> * Adjusted to new folder structure
> v3:
> * Adding Kconfig-depends and #if's
> (so basically adding similar dependancy constraints as the bridge code
> has, except that there are no depends if batman-adv gets compiled without
> multicast optimizations)
> -> the case of IPv6=M and batman-adv=y is still impossible if multicast
> optimizations are enabled; but I don't see the practical demand for that
> either - people who use IPv6 as a module will probably also want to
> use batman-adv as a module
> v2:
> * various bugfixes (now runtime tested, too - should(tm) work)
> * added netdev+bridge mailinglists
prev parent reply other threads:[~2015-05-06 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 19:29 [B.A.T.M.A.N.] [PATCHv5 0/3] batman-adv: Unicasting multicast reports to querier-node only Linus Lüssing
2015-05-06 19:29 ` [B.A.T.M.A.N.] [PATCHv5 1/3] batman-adv: Forward IGMP/MLD reports to selected querier (only) Linus Lüssing
2015-05-06 19:29 ` [B.A.T.M.A.N.] [PATCHv5 2/3] batman-adv: Increase BATADV_TVLV_MCAST version number to 2 Linus Lüssing
2015-05-06 19:29 ` [B.A.T.M.A.N.] [PATCHv5 3/3] compat: Compat code for IGMP/MLD report unicast forwarding Linus Lüssing
2015-05-07 7:33 ` Sven Eckelmann
2015-05-17 0:40 ` Linus Lüssing
2015-05-06 19:38 ` Linus Lüssing [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=20150506193856.GJ2423@odroid \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.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.