From: Jonathan Morton <chromatix99@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] More overhead keywords
Date: Mon, 18 May 2015 03:49:09 +0300 [thread overview]
Message-ID: <AE88AA8A-6B7A-4FCB-A482-66659015802D@gmail.com> (raw)
In-Reply-To: <CANmMgnHwVVZ7SEy=eg6cSJ9LLubrbmXaHqA5M-VN4VvNQH5Z+w@mail.gmail.com>
This is entirely userspace (ie. iproute2) stuff:
The initial cake-overhead patch included only “raw” and “conservative” shortcut keywords, alongside the numeric “overhead” parameter for experts. I’ve now worked out an extended set of keywords which, I think, takes care of all the normal cases.
There are eight new keywords which deal with the basic ADSL configurations. These switch on ATM cell-framing compensation, and set the overhead based on the raw IP packet as a baseline.
ipoa-vcmux (8)
ipoa-llcsnap (16)
bridged-vcmux (24)
bridged-llcsnap (32)
pppoa-vcmux (10)
pppoa-llc (14)
pppoe-vcmux (32)
pppoe-llcsnap (40)
Note that “pppoa-llc” is not a typo - it really doesn’t involve SNAP, and is thus a little more compact than if it did.
Two more new keywords deal with the basic VDSL2 configurations. Again, the overheads use IP as a baseline, but this time ATM cell-framing is turned off. Apparently PTM does have a small additional overhead on the order of 1/128, due to HDLC framing which attaches special meaning to 0x7D and 0x7E bytes; I might need to add approximate handling for that, kernel-side.
pppoe-ptm (27)
bridged-ptm (19)
The final three keywords are not for standalone use, but act as modifiers to some previous keyword. They can be specified more than once, which is probably only useful for “ether-vlan”.
via-ethernet (-14)
ether-fcs (+4)
ether-vlan (+4)
Does all this look reasonable? In particular, have I missed anything regarding PTM/VDSL2? I’m using http://www.ethernetinthefirstmile.com/articles/WTC2002.pdf as a reference, but it isn’t as clear as it might be.
- Jonathan Morton
next prev parent reply other threads:[~2015-05-18 0:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 14:02 [Cake] openwrt build with latest cake and other qdiscs Alan Jenkins
2015-05-10 17:29 ` Alan Jenkins
2015-05-10 20:37 ` Dave Taht
2015-05-10 20:38 ` Dave Taht
2015-05-11 6:54 ` Sebastian Moeller
2015-05-10 21:46 ` Sebastian Moeller
2015-05-10 22:19 ` Dave Taht
2015-05-11 6:50 ` Sebastian Moeller
2015-05-11 7:01 ` Jonathan Morton
2015-05-13 6:43 ` Jonathan Morton
2015-05-14 9:19 ` Sebastian Moeller
2015-05-14 10:24 ` Jonathan Morton
2015-05-14 10:33 ` Alan Jenkins
2015-05-14 10:42 ` Jonathan Morton
2015-05-14 10:58 ` Sebastian Moeller
2015-05-14 13:12 ` Jonathan Morton
2015-05-14 14:57 ` Sebastian Moeller
2015-05-14 15:32 ` Jonathan Morton
2015-05-14 18:15 ` Sebastian Moeller
2015-05-14 22:06 ` Jonathan Morton
2015-05-15 2:27 ` Dave Taht
2015-05-15 21:49 ` Jonathan Morton
2015-05-14 9:50 ` Alan Jenkins
2015-05-18 0:49 ` Jonathan Morton [this message]
2015-05-18 7:27 ` [Cake] More overhead keywords Sebastian Moeller
2015-05-18 8:13 ` Jonathan Morton
2015-05-18 8:41 ` Sebastian Moeller
2015-05-18 19:41 ` David Lang
2015-05-18 19:57 ` Dave Taht
2015-05-19 10:14 ` Kevin Darbyshire-Bryant
2015-05-23 0:30 ` Dave Taht
2015-05-23 2:27 ` Jonathan Morton
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AE88AA8A-6B7A-4FCB-A482-66659015802D@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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