From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] overheads or rate calculation changed?
Date: Sun, 24 Dec 2017 13:19:16 +0100 [thread overview]
Message-ID: <58D662F6-860D-46A5-A6C5-343D1305055B@gmx.de> (raw)
In-Reply-To: <038238AD-D523-4C5A-8215-555616FA28FD@darbyshire-bryant.me.uk>
Hi Kevin, hi all,
On December 24, 2017 11:46:31 AM GMT+01:00, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>
>> On 24 Dec 2017, at 10:39, Jonathan Morton <chromatix99@gmail.com>
>wrote:
>>
>> If you combine the 'raw' keyword with an overhead spec, that disables
>the hard_header_len compensation.
>>
>> - Jonathan Morton
>
>Indeed. I think all I’m proving is ‘make something idiot
>proof…..they’ll only go and improve the idiot’… i.e. me :-)
Haha, funny ;). But with the current state of the cake correcting for hard_header_len, while this is not guaranteed to be the overhead the kernel adds to skb->Len; I would claim cake is not idiot proof, but rather has a very tricky default mode...
I do add that reporting max_len_after_overhead_accounting in addition to max_len would have made it much more likely to catch this behaviour much earlier...
Best Regards & happy holidays
Sebastian
>
>
>Happy holiday season to all. I’m off to find another trap to fall into
>;-)
>
>Cheers,
>
>Kevin D-B
>
>012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-12-24 12:19 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
2017-12-24 10:39 ` Jonathan Morton
2017-12-24 10:46 ` Kevin Darbyshire-Bryant
2017-12-24 12:19 ` Sebastian Moeller [this message]
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=58D662F6-860D-46A5-A6C5-343D1305055B@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=kevin@darbyshire-bryant.me.uk \
/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