All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Marek Lindner <mareklindner@neomailbox.ch>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/1] batman-adv: Always flood IGMP/MLD reports
Date: Mon, 29 Jun 2015 06:42:46 +0200	[thread overview]
Message-ID: <20150629044246.GD2527@odroid> (raw)
In-Reply-To: <20150629025248.GC2527@odroid>

On Mon, Jun 29, 2015 at 04:52:48AM +0200, Linus Lüssing wrote:
> The alternative to bumping the version number would be to introduce
> another flag into the mcast tvlv and keep counters and lists similar
> to the num_disabled or want_* ones. So maybe about 80 more lines of
> code and additional state and complexity to maintain.

Another alternative I just had to think about would be to register
both a v1 and v2 TVLV container while only registering a handler
for v2. That'd add just two or four extra lines of code with the same
result. The disadvantage would be a few bytes extra overhead for
dragging a v1 TVLV in the OGMs along.

Actually, I think I'd kinda like that as it has a reasonable
benefit-to-cost ratio. What do others think?

(And maybe such legacy multicast v1 TVLV could then safely be
obsoleted/removed in four years or after evaluating whether someone
still needs it.)

  reply	other threads:[~2015-06-29  4:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21 13:36 [B.A.T.M.A.N.] [PATCH 0/1] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2015-06-21 13:36 ` [B.A.T.M.A.N.] [PATCH 1/1] " Linus Lüssing
2015-06-26 12:43   ` Simon Wunderlich
2015-06-28  1:37   ` Marek Lindner
2015-06-28  3:59     ` Linus Lüssing
2015-06-28 13:21       ` Marek Lindner
2015-06-29  2:52         ` Linus Lüssing
2015-06-29  4:42           ` Linus Lüssing [this message]
2015-06-22 17:55 ` [B.A.T.M.A.N.] [PATCH 0/1] " Linus Lüssing

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=20150629044246.GD2527@odroid \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mareklindner@neomailbox.ch \
    /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.