From: Sven Eckelmann <sven@narfation.org>
To: 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, 22 Jan 2017 14:08:50 +0100 [thread overview]
Message-ID: <7073965.bG8vkJTefB@sven-edge> (raw)
In-Reply-To: <20161219112535.9446-1-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
On Montag, 19. Dezember 2016 12:25:29 CET Linus Lüssing wrote:
> Hi,
>
> Here is a first patchset to reintroduce aggregation support for BATMAN V, too.
> And while at it, for BATMAN VI, VII... etc, as well - in fact, it allows
> aggregating any batman packet with a broadcast destination ;).
>
> I am sending it as an RFC for now as compat code is still missing. And although
> it was tested in VMs, I still need to do some stress testing on some
> embedded routers.
I have not actually looked at the code. But I would guess that your ultimate
goal is to reduce the overhead when sending broadcast either over wifi or
complex setups with things like VPNs (fastd). Did you do some captures on some
gluon supernodes (or actually only on a link to this supernode) and calculated
how many packets/bytes were sent over the DSL (up/down), how much overhead was
added, how many packets would potentially be aggregated by your approach and
how many packets/bytes would have been send over the DSL (up/down)?
Sounds to me at least like something which could be done on some existing
setups with some small script/program reading a pcap, creating some input
for some simulator and then sending this data through the actual simulator.
And this all without having to actually break a working system :)
I think Simon (or I should also) have a very recent dump for a 2 1/2 days test
which captured (bcast/mcast/batman overhead) data from a spare Freifunk
Vogtland node (its ethernet port) without any clients attached. This would be
a potential source of test data (which we would have to anonymize for the
simulator input).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-22 13:08 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 ` Sven Eckelmann [this message]
2017-01-29 13:10 ` [B.A.T.M.A.N.] [RFC PATCH 0/6] batman-adv: broadcast packet aggregation Linus Lüssing
2017-01-29 13:15 ` 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=7073965.bG8vkJTefB@sven-edge \
--to=sven@narfation.org \
--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