From: Eric Dumazet <eric.dumazet@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, 07 May 2012 22:03:40 +0200 [thread overview]
Message-ID: <1336421020.3752.2359.camel@edumazet-glaptop> (raw)
In-Reply-To: <4FA82422.9040500@freedesktop.org>
On Mon, 2012-05-07 at 15:36 -0400, Jim Gettys wrote:
> 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.
>
SFB, one of the latest qdisc added in linux has ECN support enabled.
There is no option to disable it, because I felt it was safe. Maybe I
was a fool, but problem is I am not sure SFB is even used.
> 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).
Since ECN is not mentioned in Codel paper, this means no simulation was
done to study the possible effects.
So its probably better to leave ECN as an option. We can change the
default later.
next prev parent reply other threads:[~2012-05-07 20:03 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
2012-05-07 20:03 ` Eric Dumazet [this message]
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=1336421020.3752.2359.camel@edumazet-glaptop \
--to=eric.dumazet@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