From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Ryan Mounce <ryan@mounce.com.au>, Cake List <Cake@lists.bufferbloat.net>
Subject: Re: [Cake] overheads or rate calculation changed?
Date: Sun, 24 Dec 2017 10:34:15 +0000 [thread overview]
Message-ID: <F440A34F-8722-4A46-8D5F-1BF910637B48@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <7416D2DC-A95B-40EA-B7AB-000BF9D113F8@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
> On 23 Dec 2017, at 21:03, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi All,
>
> just had a look for hard_header_len in the linux kernel:
> linux/include/linux/netdevice.h:
> * @hard_header_len: Maximum hardware header length.
> * @min_header_len: Minimum hardware header length
>
> this seems to corroborate our observation that hard_header_len is not a veridical representation of the actual hardware header length, so I assume the values cake returns are actually true. It also indicates that except for pure ethernet interfaces hard_header_len is _not_ the right parameter to evaluate for what cake is evaluating it for...
What came as a surprise to me the other day is that whatever ‘overhead’ you specify on the command line must *include* the hard_header_len figure, since the code subtracts ‘hard header len’ from the passed overhead value. I’ve probably been doing this wrong for… who knows how long.
if (tb[TCA_CAKE_OVERHEAD]) {
if (tb[TCA_CAKE_ETHERNET]) <<<— this is really a synonym for ‘raw’, in my case it isn’t passed so else is exec
q->rate_overhead = -(nla_get_s32(tb[TCA_CAKE_ETHERNET]));
else
q->rate_overhead = -(qdisc_dev(sch)->hard_header_len); <<<—note the sneaky minus!
q->rate_overhead += nla_get_s32(tb[TCA_CAKE_OVERHEAD]);
For a while I’ve manually been passing ’12’ as a ‘bridged-ptm ether-vlan’ equivalent except I should have been passing ’26’. Instead I’ve been reducing the length of packets by 2 bytes :-) I now just pass the relevant keywords.
Cheers,
Kevin D-B
Falling into traps so you don’t have to(tm)
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-24 10:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 20:32 Andy Furniss
2017-12-21 0:54 ` Andy Furniss
2017-12-22 6:38 ` Jonathan Morton
2017-12-22 7:58 ` Kevin Darbyshire-Bryant
[not found] ` <CAJq5cE3e-CbJ8X_Bpu3AhwbVmq-yD89HGe7rSNMTYqj+KSaBUg@mail.gmail.com>
2017-12-22 10:00 ` Jonathan Morton
2017-12-22 12:58 ` Kevin Darbyshire-Bryant
2017-12-22 15:55 ` Dave Taht
2017-12-22 23:38 ` Andy Furniss
2017-12-23 9:41 ` Sebastian Moeller
2017-12-23 9:59 ` Andy Furniss
2017-12-23 12:55 ` Sebastian Moeller
2017-12-23 13:11 ` Ryan Mounce
2017-12-23 14:21 ` Sebastian Moeller
2017-12-23 21:03 ` Sebastian Moeller
2017-12-23 21:20 ` Jonathan Morton
2017-12-24 10:34 ` Kevin Darbyshire-Bryant [this message]
2017-12-24 10:39 ` Jonathan Morton
2017-12-24 10:46 ` Kevin Darbyshire-Bryant
2017-12-24 12:19 ` Sebastian Moeller
2017-12-24 12:14 ` Sebastian Moeller
2018-01-06 20:44 ` Jonathan Morton
2018-01-06 22:46 ` Sebastian Moeller
2018-01-07 0:33 ` Jonathan Morton
2018-01-07 8:19 ` Sebastian Moeller
2018-01-07 15:21 ` 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=F440A34F-8722-4A46-8D5F-1BF910637B48@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=Cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=ryan@mounce.com.au \
/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