From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v6 0/3] batman-adv: add dynamic, bridged-in TT VID detection
Date: Fri, 9 May 2025 16:17:56 +0200 [thread overview]
Message-ID: <aB4OlGLxvaAQt0zf@sellars> (raw)
In-Reply-To: <20250221-dynamic-vlans-v6-0-fd94c9b782a7@narfation.org>
I also got some before and after OGMv1 overhead test results
with this patchset and the VID 0 remapping patch, averaged over
one week. Not as significant as the pending DAT patchset, but still
a -15.94% OGM overhead saving on our ~200 nodes network.
The theoretical upper limit would have been 23.5% with a raw OGM
message size of 68 bytes reduced to 52 bytes. The measured 15.94%
also includes +14 bytes ethernet frame size and batman-adv aggregation
though. The more OGMs are aggregated, the closer you'd get to a
23.5% saving.
$ capinfos ogmv1-1week-before.cap:
...
Data bit rate: 43 kbps
Average packet size: 212.77 bytes
Average packet rate: 25 packets/s
...
$ capinfos ogmv1-1week-after.cap:
...
Data bit rate: 36 kbps
Average packet size: 178.84 bytes
Average packet rate: 25 packets/s
...
Regards, Linus
prev parent reply other threads:[~2025-05-09 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 17:27 [PATCH v6 0/3] batman-adv: add dynamic, bridged-in TT VID detection Sven Eckelmann
2025-02-21 17:27 ` [PATCH v6 1/3] batman-adv: add dynamic, bridged-in TT VID detection support Sven Eckelmann
2025-02-21 17:27 ` [PATCH v6 2/3] batman-adv: limit number of learned VLANs from bridged-in clients Sven Eckelmann
2026-05-14 9:43 ` Sven Eckelmann
2025-02-21 17:27 ` [PATCH v6 3/3] batman-adv: avoid adding bridge VLAN IDs through ndo_vlan_rx_add_vid() Sven Eckelmann
2026-05-14 9:43 ` Sven Eckelmann
2025-05-09 14:17 ` 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=aB4OlGLxvaAQt0zf@sellars \
--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.