From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : Added some analysis of SFQRED over wireless
Date: Tue, 10 Jan 2012 08:21:19 -0800 [thread overview]
Message-ID: <4f0c657fc9677_74343fde707abaf06475c@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 416a5de98f5bc78188c848fe666d25146b4b7084
https://github.com/dtaht/deBloat/commit/416a5de98f5bc78188c848fe666d25146b4b7084
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
A test/newsfqred/Makefile
A test/newsfqred/eps.plt
A test/newsfqred/ericping.plt
A test/newsfqred/ericpinglog.plt
A test/newsfqred/fpingflow.data
A test/newsfqred/fpingflows.data
A test/newsfqred/fpinglog.txt
A test/newsfqred/fpingsample.data
A test/newsfqred/fpingsample1.data
A test/newsfqred/parse
A test/newsfqred/pause.plt
A test/newsfqred/png.plt
A test/newsfqred/ps.plt
Log Message:
-----------
Added some analysis of SFQRED over wireless
It's good.
Commit: fc28c4f88bf4b680d11efb67a074ab87844cfa42
https://github.com/dtaht/deBloat/commit/fc28c4f88bf4b680d11efb67a074ab87844cfa42
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
M src/debloat
A test/newsfqred/README.org
Log Message:
-----------
Added notes regarding this test
I am running a continuous stress test now against the SFQ RED,
which I plan to run the rest of the night.
I am dubious of one of the plots. The curve cannot possibly
be that smooth. Can't be. I must have screwed something up.
REDSFQ is doing it's job with a few tweaks (rather than logic,
I just hit it until I started seeing more prob_mark_heads
than dropped)
qdisc mq 1: root
Sent 64534770811 bytes 43254284 pkt (dropped 77425, overlimits 111717 requeues 160859)
backlog 47808b 33p requeues 160859
qdisc sfq 10: parent 1:1 limit 300p quantum 1514b depth 127 headdrop divisor 16384
ewma 3 min 4500b max 18000b 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 414011 bytes 1406 pkt (dropped 0, overlimits 0 requeues 0)
rate 120bit 0pps backlog 0b 0p requeues 0
qdisc sfq 20: parent 1:2 limit 300p quantum 1514b depth 127 headdrop divisor 16384
ewma 3 min 4500b max 18000b 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 300p quantum 1514b depth 127 headdrop divisor 16384
ewma 3 min 4500b max 18000b probability 0.2 ecn
prob_mark 12 prob_mark_head 99610 prob_drop 0
forced_mark 0 forced_mark_head 12095 forced_drop 0
Sent 64534356800 bytes 43252878 pkt (dropped 77425, overlimits 111717 requeues 160859)
rate 104658Kbit 8763pps backlog 47808b 33p requeues 160859
qdisc sfq 40: parent 1:4 limit 300p quantum 1514b depth 127 headdrop divisor 16384
ewma 3 min 4500b max 18000b 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
Compare: https://github.com/dtaht/deBloat/compare/4a6653c...fc28c4f
reply other threads:[~2012-01-10 16:21 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=4f0c657fc9677_74343fde707abaf06475c@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