From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] openwrt was changing fq_codel quantum default
Date: Tue, 8 Dec 2015 09:59:53 +0000 [thread overview]
Message-ID: <5666AA19.6080000@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Did anyone else see https://dev.openwrt.org/ticket/21326 and fixing
commit https://dev.openwrt.org/changeset/47811 go through in the early
hours of this morning?
TLDR;
q->quantum = 300; //was
q->quantum = psched_mtu(qdisc_dev(sch)); //now returned to kernel default
" i ran into cpu limits with sirq on archer c7v2 while testing ingress
shaping.
it seems to me that quantum < mtu is very costly (at cpu) with higher
(50mbps) bandwidths
~40% sirq load with quantum 1522+
90% at quantum mtu/2"
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next reply other threads:[~2015-12-08 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 9:59 Kevin Darbyshire-Bryant [this message]
2015-12-08 13:47 ` 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/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=5666AA19.6080000@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--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