From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>, a@unstable.cc
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Increase purge timeout on DAT DHT candidates
Date: Sun, 10 Feb 2019 19:50:14 +0800 [thread overview]
Message-ID: <2066898.20yZjQT5U2@rousseau> (raw)
In-Reply-To: <2472562.MHgaaGEVWG@sven-edge>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Hi,
> > 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
Sven, thanks for pointing this out. Antonio and I had to refresh our memories
on these matters since the previously rejected patch had aged 6 months by now.
The conclusion is this:
* The old patch was rejected because it was tied to IP/MAC address
combinations snooped via DHCP only (!). The magic happens inside
batadv_dat_put_pairs() which was called via the DHCP snooping path. When
comparing the old and new patch be careful as batadv_dat_put_pairs() has been
renamed to batadv_dat_put_dhcp().
With the new patch that DHCP dependency is no longer present. The way to go!
* The old patch also introduced flags being sent around which wasn't all that
necessary. This is also gone -> green light++
I'll comment on the patch itself for further simplifications.
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-10 11:50 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
2019-02-10 11:50 ` Marek Lindner [this message]
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=2066898.20yZjQT5U2@rousseau \
--to=mareklindner@neomailbox.ch \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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