From: Sebastian Moeller <moeller0@gmx.de>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Routing limit question
Date: Tue, 21 Oct 2014 09:43:40 +0200 [thread overview]
Message-ID: <88133141-A68D-44FE-B41D-6FB7D8C4AAEC@gmx.de> (raw)
In-Reply-To: <CALQXh-M1zLNF8PXt=L55nLQkvMZzgwFRsQTr7tUY+cgNxehp2g@mail.gmail.com>
Hi Aaron,
On Oct 21, 2014, at 05:35 , Aaron Wood <woody77@gmail.com> wrote:
> On Mon, Oct 20, 2014 at 3:48 PM, Dave Taht <dave.taht@gmail.com> wrote:
> OK, I tried a few combinations of burst and cburst on a cerowrt box,
> using 90/10 as a up/download speed.
>
> burst 64000 cburst 64000 was a bit of a win, in most respects, but odd
> in others.
>
> Interesting.... can this be specified on the advanced options string (ingress only)?
Unfortunately not, the advanced option string is just passed to the leaf qdiscs, but if you are willing to edit simple.qos you can change:
LQ="quantum `get_mtu $IFACE $CEIL`”
into:
LQ="quantum `get_mtu $IFACE $CEIL` burst 64000 cburst 64000” for either ingress or egress or both to get the desired effect. As always “tc class show dev ge00” and "tc class show dev ifb4ge00” should show you wether your changes took hold (assuming you use a recent sqm-scripts and ge00…).
So I probably will try to expose these options in an additional optional hidden-by-default entry fields in a future revision.
Best Regards
Sebastian
>
> -Aaron
next prev parent reply other threads:[~2014-10-21 7:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 17:51 Ernesto Elias
2014-10-19 18:24 ` Dave Taht
2014-10-19 18:48 ` Ernesto Elias
2014-10-19 18:51 ` Dave Taht
2014-10-19 19:16 ` Ernesto Elias
2014-10-19 19:55 ` Sebastian Moeller
2014-10-20 1:08 ` Ernesto Elias
2014-10-20 8:11 ` Sebastian Moeller
2014-10-21 2:30 ` Ernesto Elias
2014-10-21 8:23 ` Sebastian Moeller
2014-10-22 19:39 ` Ernesto Elias
2014-10-22 20:36 ` Sebastian Moeller
2014-10-23 22:03 ` Ernesto Elias
2014-10-24 11:38 ` Sebastian Moeller
2014-10-19 18:56 ` Sebastian Moeller
2014-10-19 19:22 ` Dave Taht
2014-10-19 19:33 ` Ernesto Elias
2014-10-19 19:41 ` Dave Taht
[not found] ` <CAA93jw6DFxoDaRVCoQn=zxbOjgQ-dA1bCZ1W=p9br25jWrRgkg@mail.gmail.com>
2014-10-19 22:44 ` Sebastian Moeller
2014-10-20 20:04 ` Dave Taht
2014-10-20 22:48 ` Dave Taht
2014-10-21 3:35 ` Aaron Wood
2014-10-21 7:43 ` Sebastian Moeller [this message]
2014-10-21 7:51 ` Sebastian Moeller
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88133141-A68D-44FE-B41D-6FB7D8C4AAEC@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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