From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [RFC PATCH 0/6] batman-adv: broadcast packet aggregation
Date: Sun, 29 Jan 2017 14:15:32 +0100 [thread overview]
Message-ID: <20170129131532.GD6468@otheros> (raw)
In-Reply-To: <20170129130959.GC6468@otheros>
On Sun, Jan 29, 2017 at 02:10:00PM +0100, Linus Lüssing wrote:
> For instance the VPN tool "fastd", would add additional
> headers in sizes of up to 86 bytes (40B IPv6 + 46B UDP+fastd) [1].
> Therefore reducing the number of broadcast packets by 2.79 should
> reduce the effective multicast bitrate of:
[...]
[1]: https://twitter.com/ffhhnoc/status/787771192853798915
(Diagram regarding encapsulation overhead with fastd + batman-adv)
prev parent reply other threads:[~2017-01-29 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 11:25 [B.A.T.M.A.N.] [RFC PATCH 0/6] batman-adv: broadcast packet aggregation Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 1/6] batman-adv: Allow TVLVs greater than 128 bytes Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 2/6] batman-adv: aggregation packet reception Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 3/6] batman-adv: aggregation packet queueing and transmission Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 4/6] batman-adv: privatize forw_packet skb assignment Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 5/6] batman-adv: restructure rebroadcast counter into forw_packet API Linus Lüssing
2016-12-19 11:25 ` [B.A.T.M.A.N.] [RFC PATCH 6/6] batman-adv: do not aggregate rebroadcasts in the same packet Linus Lüssing
2017-01-22 13:08 ` [B.A.T.M.A.N.] [RFC PATCH 0/6] batman-adv: broadcast packet aggregation Sven Eckelmann
2017-01-29 13:10 ` Linus Lüssing
2017-01-29 13:15 ` Linus Lüssing [this message]
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=20170129131532.GD6468@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 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.