public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv9 0/4] Multicast optimizations for bridges
Date: Sun, 23 Nov 2014 17:14:11 +0100	[thread overview]
Message-ID: <2037698.Rp78ARo8W2@prime> (raw)
In-Reply-To: <1410068560-7829-1-git-send-email-linus.luessing@web.de>

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

On Sunday 07 September 2014 07:42:36 Linus Lüssing wrote:
> This patchset enables the usage of the batman-adv multicast optimizations
> for scenarios involving bridges on top of e.g. bat0, too.
> 
> Along come two more patches adding according debugging facilities
> to make it possible for the user to check why the multicast
> optimizations might not work ideally to give hints about
> what they might change about their topology.
> 
> The fourth one alters the forwarding behaviour for IGMP and MLD
> reports. For one thing this reduces overhead (especially for IGMPv3/MLDv2
> reports). But more importantly this is necessary to make the
> optimizations work in bridged scenarios at all. For more details see:
> http://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-li
> stener-reports

As discussed it would be great to clarify the text on that wiki page a little. 
It is not really clear (at least to me) why this is necessary. Simple english 
and not too many conditions and integrated remarks help. :)

> 
> Also note, that with PATCH 4/4 multicast optimizations do not build
> for kernels < 2.6.35 (net/mld.h didn't exist back then): If there are
> actually brave souls out there running such ancient end-of-life kernels,
> it is suggested to build batman-adv with the multicast-compile-time option
> disabled. Multicast optimizations for bridges does not half any benefits
> for kernels < 3.17 anyways.

How about you add some kind of #error in compat.h if multicast is enabled and 
the kernel is too old, and ask to disable the multicast feature? that should 
be better then just failing with "mld.h not found".  Otherwise we could add a 
stub mld.h and stub compat functions as we do for newer kernels which do not 
yet support all the multicast fun.

Thanks
    Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2014-11-23 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07  5:42 [B.A.T.M.A.N.] [PATCHv9 0/4] Multicast optimizations for bridges Linus Lüssing
2014-09-07  5:42 ` [B.A.T.M.A.N.] [PATCHv9 1/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2014-09-07  5:42 ` [B.A.T.M.A.N.] [PATCHv9 2/4] batman-adv: Adding 'mcast' log level Linus Lüssing
2014-09-07  5:42 ` [B.A.T.M.A.N.] [PATCHv9 3/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2014-09-07  5:42 ` [B.A.T.M.A.N.] [PATCHv9 4/4] batman-adv: Forward IGMP/MLD reports to selected querier (only) Linus Lüssing
2014-11-24 14:56   ` Simon Wunderlich
2014-11-26 16:37     ` Linus Lüssing
2014-11-23 16:14 ` Simon Wunderlich [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=2037698.Rp78ARo8W2@prime \
    --to=sw@simonwunderlich.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox