public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] [PATCH 2/2] batman-adv: Use own timer for multicast TT and TVLV updates
Date: Thu, 21 Jul 2016 23:53:51 +0200	[thread overview]
Message-ID: <20160721215351.GL10173@otheros> (raw)
In-Reply-To: <1469137112-24094-2-git-send-email-linus.luessing@c0d3.blue>

On Thu, Jul 21, 2016 at 11:38:32PM +0200, Linus Lüssing wrote:
> Instead of latching onto the OGM period, this patch introduces a worker
> dedicated to multicast TT and TVLV updates.
> 
> The reasoning is, that upon roaming especially the translation table
> should be updated timely to minimize connectivity issues.
> 
> With BATMAN V, the idea is to greatly increase the OGM interval to
> reduce overhead. Unfortunately, right now this could lead to
> a bad user experience if multicast traffic is involved.
> 
> Therefore this patch introduces a fixed 500ms update interval for
> multicast TT entries and the multicast TVLV.

PS: And as a side-effect, removes the funny locking dependency
with the TT commit lock. Had still been nagging me, this tight
coupling between MC and TT.

  reply	other threads:[~2016-07-21 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 21:38 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Remove unnecessary lockdep in batadv_mcast_mla_list_free Linus Lüssing
2016-07-21 21:38 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Use own timer for multicast TT and TVLV updates Linus Lüssing
2016-07-21 21:53   ` Linus Lüssing [this message]
2016-07-21 21:59   ` Sven Eckelmann
2016-07-21 22:19     ` Sven Eckelmann
2016-08-01 20:57       ` Linus Lüssing
2016-08-02  7:44         ` Sven Eckelmann
2016-07-21 22:01 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Remove unnecessary lockdep in batadv_mcast_mla_list_free Sven Eckelmann

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=20160721215351.GL10173@otheros \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox