From: Jim Gettys <jg@freedesktop.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
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, 07 May 2012 15:36:02 -0400 [thread overview]
Message-ID: <4FA82422.9040500@freedesktop.org> (raw)
In-Reply-To: <1336418211.3752.2353.camel@edumazet-glaptop>
On 05/07/2012 03:16 PM, Eric Dumazet wrote:
> On Mon, 2012-05-07 at 14:50 -0400, Jim Gettys wrote:
>
>> You want to turn it on in CeroWrt: sure. Expert audience, who may be
>> able to notice when things go sour, fine....
>>
>> Neither you, nor I are expert at the current state of ECN in the global
>> Internet: but Steve Bauer is. We can have that conversation with him
>> shortly.
>>
>> So for now "First, do no harm" should be our mantra....
>>
>> So the upstream patch default state should be off. We don't want to mix
>> "codel doesn't work" with "ecn is busted someplace", as it gets its trials.
>>
> ecn is negociated by peers, not a qdisc.
>
> ecn at qdisc level is only marking an already enabled ECN packet.
>
> Since most packets are not ECN enabled, they are dropped instead.
That's certainly the way ECN is supposed to work right now.
>
> If you read my ECN addition to Codel, you can see its disabled by
> default already. Its a toy for early adopters.
I think it is safe for it to behave the rest of the way Linux ECN
support does right now: it only gets used if the peer requests it.
Not clear to me there needs to be/should be any option at all: the last
conversation I had with Steve Bauer was that something north of 20% of
conversations were ECN capable. Is there one for the other instances of
ECN support in Linux? If so, it should be keyed by the same variable,
and not be a one-off for codel.
If you wanted to test ECN separately from drop with codel, then you'd
just request ECN in the conversation (by default, OS's don't normally
request ECN today, as the remaining brokenness gets sorted out).
- Jim
next prev parent reply other threads:[~2012-05-07 19:36 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
2012-05-07 18:50 ` Jim Gettys
2012-05-07 19:16 ` Eric Dumazet
2012-05-07 19:36 ` Jim Gettys [this message]
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=4FA82422.9040500@freedesktop.org \
--to=jg@freedesktop.org \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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