From: Kathleen Nichols <nichols@pollere.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Pointer to Van's Queue Rant and a small plea on AQMs
Date: Wed, 09 Feb 2011 16:51:06 -0800 [thread overview]
Message-ID: <4D53367A.7030109@pollere.com> (raw)
I've read through the posts here and Jim's slides and this is a great
topic. I hope progress
is made.
I thought I'd supply a pointer to a talk (a rant) Van gave in July of
06. I believe he reused
some of this in another talk last year, but here it is:
http://pollere.net/Pdfdocs/QrantJul06.pdf
Also, as someone who spent a lot of time examining the dysfunctionality
of 93 RED and
various changes Van came up with in response to the problems: examine
any AQM very
carefully. It's likely not working the way you think it is. What I
learned is that almost
anything works with nicely behaved long-lived TCPs and that almost
nothing works
well with mixtures of mice and elephants. It's also instructive to
examine what is really
happening when your AQM drops packets. We found that 93 RED spent a lot
of time
doing what we called "forced drops" which means you are in the "drop
everything"
part of your control law. What we would find with 93 RED were a bunch of
back to
back drops. There's tons of stuff on this in our unfinished "RED in a
different light"
paper, but look at the first 10 slides or so of
http://pollere.net/Pdfdocs/bcit_6.2001.pdf
and you'll see some of it without wading through a lot of boring prose.
So, please, please, don't make a "fix" that is perhaps worse than the
original problem.
Kathie
(also known as "Van's wife Kathy")
next reply other threads:[~2011-02-10 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 0:51 Kathleen Nichols [this message]
2011-02-10 1:33 ` Eric Raymond
2011-02-10 19:15 ` Juliusz Chroboczek
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D53367A.7030109@pollere.com \
--to=nichols@pollere.com \
--cc=bloat@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