public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>, mareklindner@neomailbox.ch
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Increase purge timeout on DAT DHT candidates
Date: Sat, 02 Feb 2019 06:14:41 +0100	[thread overview]
Message-ID: <2472562.MHgaaGEVWG@sven-edge> (raw)
In-Reply-To: <20190111210208.29139-1-linus.luessing@c0d3.blue>

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

On Friday, 11 January 2019 22.02.08 CET Linus Lüssing wrote:
> Currently, the DHT_GET messages of the DAT will likely be left
> unanswered due to the following issues:
[...]
> With this patch the purge timeout for local DAT cache entries and
> entries submitted via a DHT_PUT message is differentiated:
> 
> While the former stays at 5min. the latter is increased to 30min. Which
> decreases the rate of broadcasted ARP Requests.
> 
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>

@Marek, if I remember correctly, you had some issues [1] with this approach. 
Could you please check again

Kind regards,
	Sven

[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2018-June/017881.html

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

  reply	other threads:[~2019-02-02  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 21:02 [B.A.T.M.A.N.] [PATCH] batman-adv: Increase purge timeout on DAT DHT candidates Linus Lüssing
2019-02-02  5:14 ` Sven Eckelmann [this message]
2019-02-10 11:50   ` Marek Lindner
2019-02-10 11:59 ` Marek Lindner
2019-02-10 15:09   ` Linus Lüssing
2019-02-10 22:21     ` Antonio Quartulli
2019-02-11  7:51       ` Linus Lüssing
2019-04-07 11:09   ` 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=2472562.MHgaaGEVWG@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linus.luessing@c0d3.blue \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox