From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] The next slice of cake
Date: Sun, 22 Mar 2015 17:29:45 +0200 [thread overview]
Message-ID: <6AA447D2-6148-464C-908D-98160A0E24C7@gmail.com> (raw)
In-Reply-To: <51665FD7-629A-4B8C-B258-2E9AF8E3B5D0@gmx.de>
>>> On 22 Mar, 2015, at 11:39, Sebastian Moeller <moeller0@gmx.de> wrote:
>>>
>>> I could be out to lunch here, as usual,;but I argue the byte limit should include the kernel overhead (could this be based on skb->truesize) as this is what counts against real memory. My assumption here is that in normal operation we rarely/never get queues to fill up to the limit anyways
>>
>> Such an argument could certainly be made. Does skb->truesize include the skb header, as well as the buffer space allocated?
>
> According to http://vger.kernel.org/~davem/skb_sk.html (“We keep track of how many bytes of system memory are consumed by a packet in 'skb->truesize'. This is the total of how large a data buffer we allocated for the packet, plus the size of 'struct sk_buff' itself.") it looks like this should be the right number, but I am not well versed in reading kernel code, so there might be some caveats I am not aware of.
The statement in that commentary seems to be authoritative enough to rely on.
>>> (as tho would turn the queue into tail-drop effectively)
>>
>> But fq_codel (and cake) are a little cleverer than that, even when they hit the hard limit. They still drop from the head, and they shoot the longest flow-queue first.
>
> Excellent, learned something new today; in fq_codel does this come from the per-codel instance 1000 packet limit or from the default fq_codel 102400? packet limit (just in case someone knows off hand, I can try to understand the kernel code myself, given enough time ;) )?
Off the top of my head, most likely both. (If a per-queue limit is hit, then by definition that’s the longest queue.)
I should probably re-read the code to be certain of that, though. I’m currently eyeball-deep in running software updates on half a dozen very obsolete machines, and cracking the cases on half a dozen routers to see what hardware they’ve got inside. So far I think *one* of them has actually matched what the OpenWRT database lists, and even then there’s an obvious error.
- Jonathan Morton
next prev parent reply other threads:[~2015-03-22 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:08 Jonathan Morton
2015-03-18 7:22 ` Sebastian Moeller
2015-03-18 8:41 ` Jonathan Morton
2015-03-18 10:39 ` Sebastian Moeller
2015-03-18 15:10 ` Kathleen Nichols
2015-03-18 15:20 ` Jonathan Morton
2015-03-18 21:20 ` Dave Taht
2015-03-21 16:09 ` Dave Taht
2015-03-21 23:55 ` Jonathan Morton
2015-03-22 9:39 ` Sebastian Moeller
2015-03-22 10:43 ` Jonathan Morton
2015-03-22 12:51 ` Sebastian Moeller
2015-03-22 15:29 ` Jonathan Morton [this message]
2015-03-30 17:28 ` Jonathan Morton
2015-03-30 18:23 ` Sebastian Moeller
2015-03-31 3:22 ` Jonathan Morton
2015-03-31 7:12 ` Sebastian Moeller
2015-03-31 12:47 ` Jonathan Morton
2015-03-30 19:28 ` Dave Taht
2015-04-02 4:48 ` Jonathan Morton
2015-04-02 5:17 ` Dave Taht
2015-04-02 5:19 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6AA447D2-6148-464C-908D-98160A0E24C7@gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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