From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.3.8-17 is released
Date: Wed, 15 Aug 2012 21:58:05 -0700 [thread overview]
Message-ID: <CAA93jw4AYY5J9h66v7mLHh3s-HaTkAW7fE1q-QFU-G=HBixcbQ@mail.gmail.com> (raw)
In-Reply-To: <CE5E0FFF-3A0B-467A-B781-286F0E0AB631@gmx.de>
Firstly fq_codel will always stay very flat relative to your workload
for sparse streamss such as a ping or voip dns or gaming...
It's good stuff.
And, I think the source of your 2.8 second thing is fq_codel's current
reaction time, the non-responsiveness of the udp flooding netanylzer
uses
and huge default queue depth in openwrt's qos scripts.
Try this:
cero1@snapon:~/src/Cerowrt-3.3.8/package/qos-scripts/files/usr/lib/qos$
git diff tcrules.awk
diff --git a/package/qos-scripts/files/usr/lib/qos/tcrules.awk
b/package/qos-scripts/files/usr/lib/qos/tcrules
index a19b651..f3e0d3f 100644
--- a/package/qos-scripts/files/usr/lib/qos/tcrules.awk
+++ b/package/qos-scripts/files/usr/lib/qos/tcrules.awk
@@ -79,7 +79,7 @@ END {
# leaf qdisc
avpkt = 1200
for (i = 1; i <= n; i++) {
- print "tc qdisc add dev "device" parent 1:"class[i]"0
handle "class[i]"00: fq_codel"
+ print "tc qdisc add dev "device" parent 1:"class[i]"0
handle "class[i]"00: fq_codel limit 1200
}
# filter rule
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"
next prev parent reply other threads:[~2012-08-16 4:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 6:08 Dave Taht
2012-08-13 16:06 ` Maciej Soltysiak
2012-08-13 16:20 ` Dave Taht
2012-08-15 17:23 ` Sebastian Moeller
2012-08-15 22:53 ` dpreed
2012-08-15 22:57 ` William Katsak
2012-08-16 4:54 ` Sebastian Moeller
2012-08-16 11:08 ` William Katsak
2012-08-16 17:02 ` dpreed
2012-08-20 18:17 ` Sebastian Moeller
2012-08-16 4:51 ` Sebastian Moeller
2012-08-16 4:58 ` Dave Taht [this message]
2012-08-16 6:09 ` Sebastian Moeller
2012-08-20 18:13 ` Sebastian Moeller
2012-08-16 4:08 ` Dave Taht
2012-08-16 5:15 ` Sebastian Moeller
2012-08-20 18:24 ` Sebastian Moeller
2012-08-21 2:33 ` dpreed
2012-08-21 2:44 ` Marchon
2012-08-21 5:28 ` Sebastian Moeller
2012-08-22 18:23 ` dpreed
2012-08-22 18:54 ` Dave Taht
2012-08-22 19:23 ` Kenneth Finnegan
2012-08-22 20:44 ` Dave Taht
2012-08-21 5:23 ` Sebastian Moeller
2012-08-17 8:52 ` [Cerowrt-devel] cerowrt 3.3.8-17: nice latency improvements, some issues with bind Török Edwin
2012-08-17 18:05 ` Dave Taht
2012-08-17 19:05 ` Török Edwin
2012-08-17 19:52 ` Dave Taht
2012-08-17 20:13 ` Török Edwin
2012-08-18 20:16 ` Michael Richardson
2012-08-20 20:16 ` david
2012-08-20 20:41 ` George Lambert
2012-08-20 20:48 ` david
2012-08-20 21:27 ` George Lambert
2012-08-20 23:19 ` Michael Richardson
2012-08-21 22:03 ` Maciej Soltysiak
2012-08-21 22:31 ` George Lambert
2012-08-22 1:21 ` Michael Richardson
2012-08-18 9:38 ` Török Edwin
2012-08-18 10:20 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2012-08-18 17:07 ` [Cerowrt-devel] " Dave Taht
2012-08-25 13:56 ` Török Edwin
2012-08-25 18:09 ` 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/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='CAA93jw4AYY5J9h66v7mLHh3s-HaTkAW7fE1q-QFU-G=HBixcbQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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