From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : Fix for the openwrt 'fix'
Date: Tue, 10 Jan 2012 03:01:01 -0800 [thread overview]
Message-ID: <4f0c1a6dca76d_357b3fbac62112fc194120@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 7855510b62e4ea32d722ea856727ba23d6b67c73
https://github.com/dtaht/deBloat/commit/7855510b62e4ea32d722ea856727ba23d6b67c73
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
M src/debloat
Log Message:
-----------
Fix for the openwrt 'fix'
finger foo'd the variable name
Commit: 4a6653cc4a17a10dcca5eefc1706b33a1e0ac8bb
https://github.com/dtaht/deBloat/commit/4a6653cc4a17a10dcca5eefc1706b33a1e0ac8bb
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
M src/debloat
Log Message:
-----------
Made wireless work with redsfq
Limit and depth are definately wrong, as is the divisor...
I have also seen this sort of work with both VO and BE queues
on cerowrt. I appear to be on a system now without 802.11e.
But I did have some issues, but so many things are in flight
that I have to take some steps back to thoroughly think about this
and test wireless....
and, mentally, Time in Queue is way easier...
qdisc mq 1: root
Sent 38941951 bytes 43129 pkt (dropped 0, overlimits 0 requeues 1)
backlog 0b 0p requeues 1
qdisc sfq 10: parent 1:1 limit 3000p quantum 1514b depth 127 headdrop divisor 16384
ewma 6 min 8000b max 60000b probability 0.2 ecn
prob_mark 0 prob_mark_head 0 prob_drop 0
forced_mark 0 forced_mark_head 0 forced_drop 0
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc sfq 20: parent 1:2 limit 2540p quantum 1514b depth 127 headdrop divisor 16384
ewma 6 min 8000b max 60000b probability 0.2 ecn
prob_mark 0 prob_mark_head 0 prob_drop 0
forced_mark 0 forced_mark_head 0 forced_drop 0
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc sfq 30: parent 1:3 limit 3000p quantum 1514b depth 127 headdrop divisor 16384
ewma 6 min 8000b max 60000b probability 0.2 ecn
prob_mark 0 prob_mark_head 0 prob_drop 0
forced_mark 0 forced_mark_head 0 forced_drop 0
Sent 38941951 bytes 43129 pkt (dropped 0, overlimits 0 requeues 1)
Compare: https://github.com/dtaht/deBloat/compare/e24ff88...4a6653c
reply other threads:[~2012-01-10 11:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f0c1a6dca76d_357b3fbac62112fc194120@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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