From: Dave Taht <dave.taht@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: Eric Dumazet <edumazet@google.com>,
codel@lists.bufferbloat.net,
Dave Taht <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [PATCH 1/2] codel: Controlled Delay AQM
Date: Mon, 7 May 2012 11:44:59 -0700 [thread overview]
Message-ID: <CAA93jw6ZbMuFyK5ct+Nrj2Uzb-TpUjvwSGmzG+hHi=yasn_b+A@mail.gmail.com> (raw)
In-Reply-To: <4FA81549.5060609@freedesktop.org>
On Mon, May 7, 2012 at 11:32 AM, Jim Gettys <jg@freedesktop.org> wrote:
> On 05/07/2012 01:52 PM, Dave Taht wrote:
>> ecn:
>>
>> ecn was not in the paper (and it's working well) and I'd like to live
>> in a world where ecn was the default. I think. Others disagree.
>>
>> so perhaps ecn and noecn? And ecn be the default (after some serious testing?)
>>
> I think noecn *must* be the default at the moment. There is still too
> much brokenness out there (though it is improving); Steve Bauer can
> enlighten us how much.
Possibly influenced by how hard it is to cycle builds on embedded
hardware and test one thing at a time,
as well as the space program's major success at shortening the path to
the moon, I am an advocate of all-up-testing.
http://www.nasa.gov/offices/oce/appel/ask-academy/issues/ask-oce/AO_1-7_F_snapshot.html
Going with ecn enabled by default, and being aware that it might cause
problems, will
result in less time being spent testing each individually.
I note that on an ingress qdisc ecn has mildly less risk as it only
tests the router and host device.
On egress, yes, you're testing the whole internet.
> - Jim
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-05-07 18:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 19:32 Dave Taht
2012-05-05 19:32 ` [Codel] [PATCH 2/2] codel: RED is dead Dave Taht
2012-05-05 19:47 ` [Codel] [PATCH 1/2] codel: Controlled Delay AQM Dave Taht
2012-05-05 20:05 ` Eric Dumazet
2012-05-07 16:43 ` Rick Jones
2012-05-07 17:10 ` Eric Dumazet
2012-05-07 17:18 ` Dave Taht
2012-05-07 17:27 ` Rick Jones
2012-05-07 17:34 ` Eric Dumazet
2012-05-07 17:52 ` Dave Taht
2012-05-07 18:01 ` Eric Dumazet
2012-05-07 18:09 ` Eric Dumazet
2012-05-07 18:15 ` Eric Dumazet
2012-05-07 18:32 ` Jim Gettys
2012-05-07 18:44 ` Dave Taht [this message]
2012-05-07 18:50 ` Jim Gettys
2012-05-07 19:16 ` Eric Dumazet
2012-05-07 19:36 ` Jim Gettys
2012-05-07 20:03 ` Eric Dumazet
2012-05-07 20:55 ` dave taht
2012-05-08 1:15 ` Jim Gettys
2012-05-08 1:20 ` Andrew McGregor
2012-05-08 1:45 ` Jim Gettys
2012-05-08 2:16 ` Rick Jones
2012-05-08 3:14 ` Jim Gettys
2012-05-08 3:32 ` Rick Jones
2012-05-08 3:40 ` Kathleen Nichols
2012-05-08 4:14 ` Jim Gettys
2012-05-08 5:10 ` Eric Dumazet
2012-05-08 10:25 ` Jim Gettys
2012-05-08 13:57 ` Kathleen Nichols
2012-05-08 14:04 ` Jim Gettys
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='CAA93jw6ZbMuFyK5ct+Nrj2Uzb-TpUjvwSGmzG+hHi=yasn_b+A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=edumazet@google.com \
--cc=jg@freedesktop.org \
/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