From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH v4 0/4] Broadcast Avoidances, Neighborhood Hash
Date: Sun, 5 Feb 2017 07:45:46 +0100 [thread overview]
Message-ID: <20170205064550.30262-1-linus.luessing@c0d3.blue> (raw)
Hi,
Here's the second broadcast avoidance patchset.
Hopefully, those two patchsets together should be an automatic
approach and replacement for the (non-upstream) no-rebroadcast flag
patch and the cases it is currently used for.
Documentation:
* https://www.open-mesh.org/projects/batman-adv/wiki/Broadcast-Avoidances
Branch:
* https://git.open-mesh.org/batman-adv.git/shortlog/refs/heads/linus/neighhash
Regards, Linus
-----
Known limitations: Avoidance potential is not fully detected in a setup with
a mix of 100MBit/s and 1000MBit/s capable, wired nodes.
If rebroadcast avoidance is strictly needed in such mixed, wired setups, too,
then people could consider setting the throughput_override option of BATMAN V.
next reply other threads:[~2017-02-05 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 6:45 Linus Lüssing [this message]
2017-02-05 6:45 ` [B.A.T.M.A.N.] [PATCH v4 1/4] batman-adv: Keep hard interface neighbor list sorted Linus Lüssing
2017-02-05 6:45 ` [B.A.T.M.A.N.] [PATCH v4 2/4] batman-adv: Store and transmit own neighborhood hash Linus Lüssing
2017-02-21 10:33 ` Sven Eckelmann
2017-02-05 6:45 ` [B.A.T.M.A.N.] [PATCH v4 3/4] batman-adv: Introduce packet type independent TVLV handler API Linus Lüssing
2017-02-05 9:53 ` Linus Lüssing
2017-02-05 6:45 ` [B.A.T.M.A.N.] [PATCH v4 4/4] batman-adv: Evaluate and use neighborhood hash TVLV Linus Lüssing
2017-04-25 0:53 ` [B.A.T.M.A.N.] [PATCH v4 0/4] Broadcast Avoidances, Neighborhood Hash 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=20170205064550.30262-1-linus.luessing@c0d3.blue \
--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;
as well as URLs for NNTP newsgroup(s).