From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] openwrt was changing fq_codel quantum default
Date: Tue, 8 Dec 2015 14:47:34 +0100 [thread overview]
Message-ID: <CAA93jw69jyYQF2Bp+nOMYUbuRtYoZzSEnhJHzfWWqV8B1RY8PA@mail.gmail.com> (raw)
In-Reply-To: <5666AA19.6080000@darbyshire-bryant.me.uk>
I did not like it when nbd changed the default quantum for the native qdisc.
So I support this change. That said, it has a negative effect at lower
rates (50mbit and below), when unshaped, and that bugs me also.
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
On Tue, Dec 8, 2015 at 10:59 AM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
> 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"
>
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
prev parent reply other threads:[~2015-12-08 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 9:59 Kevin Darbyshire-Bryant
2015-12-08 13:47 ` Dave Taht [this message]
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=CAA93jw69jyYQF2Bp+nOMYUbuRtYoZzSEnhJHzfWWqV8B1RY8PA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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