From: Kathleen Nichols <nichols@pollere.com>
To: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: [Codel] some useful tweaks to sfqcodel
Date: Thu, 07 Mar 2013 10:47:15 -0800 [thread overview]
Message-ID: <5138E0B3.8010808@pollere.com> (raw)
CableLabs paid for some enhancements to sfqcodel so they could do a
wider range of testing. They have generously allowed me to put that
version out. The caveat is that
there may be some bugs and we are expecting to hear about them if you
find them!
I put the links on my codel page: http://pollere.net/CoDel.html
Also, coming soon is the web client and server code for ns-2 that is
used in the CableLabs
work. This is an update and enhancement of the web client and server
code I orignally
developed for ns and ported to an old version of ns-2. Hmm, I did this a
very long time ago at two now-defunct companies. Hope Pollere doesn't go
out of business if I post
them!
Note I used packmime in the ACM paper but the web client/server allows
us to get a
measure of page load time.
Kathie
reply other threads:[~2013-03-07 18:45 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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5138E0B3.8010808@pollere.com \
--to=nichols@pollere.com \
--cc=codel@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