From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: codel sim: anybody got python skills?
Date: Thu, 31 Jan 2013 02:26:44 -0800 [thread overview]
Message-ID: <CAA93jw5HzVfqbd7ZBg7fRgKwjTiZs=k=x5WQkwgSy+KtPQQSXw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
What I'd wanted was for this
http://snapon.lab.bufferbloat.net/~d/codel_sim.py
to show
* slow start until we hit the first drop (exponential increase in delay)
* go additive (congestion avoidance)
* have the first drop start to take effect, reducing the delay somewhat
* second drop take more effect
* third drop almost succeeding
* fourth drop dropping it below target for a while, drops stopping
* going above target again, starting a drop at 1/sqrt(3)
At least it gets the invsqrt right...
(toke tossed this off before leaving for vacation, and I only got to
hacking on it at 2am this morning. Wanted to use it to illustrate codel...)
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 977 bytes --]
reply other threads:[~2013-01-31 10:26 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='CAA93jw5HzVfqbd7ZBg7fRgKwjTiZs=k=x5WQkwgSy+KtPQQSXw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=cerowrt-devel@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