From: Rich Brown <richb.hanover@gmail.com>
To: dpreed@reed.com
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Anything but "AQM"
Date: Fri, 20 Dec 2013 16:29:14 -0500 [thread overview]
Message-ID: <C68D83CC-6680-4155-9C2D-D2064D286048@gmail.com> (raw)
In-Reply-To: <1387574550.00762811@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
On Dec 20, 2013, at 4:22 PM, dpreed@reed.com wrote:
> They are based on a completely false premise - that queues should be allowed to build at all, and that local information can solve highly transient global problems.
>
> "Dumb Queue Management" is going to be far superior. Keep the queue at zero length, and try to be fair.
Maybe we should go for ATHQM - “Attila (the Hun) Queue Management”. :-)
Rich
[-- Attachment #2: Type: text/html, Size: 1844 bytes --]
next prev parent reply other threads:[~2013-12-20 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 20:07 Dave Taht
2013-12-20 20:52 ` Rich Brown
2013-12-20 21:22 ` dpreed
2013-12-20 21:29 ` Rich Brown [this message]
2013-12-20 21:36 ` Sebastian Moeller
2013-12-21 0:47 ` Rich Brown
2013-12-21 2:55 ` Dave Taht
2013-12-20 21:58 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C68D83CC-6680-4155-9C2D-D2064D286048@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
/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