From: Rick Jones <rick.jones2@hp.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: Eric Dumazet <edumazet@google.com>,
Dave Taht <dave.taht@bufferbloat.net>,
codel@lists.bufferbloat.net
Subject: Re: [Codel] [PATCH 1/2] codel: Controlled Delay AQM
Date: Mon, 07 May 2012 19:16:22 -0700 [thread overview]
Message-ID: <4FA881F6.9080808@hp.com> (raw)
In-Reply-To: <4FA87ABC.4080907@freedesktop.org>
On 05/07/2012 06:45 PM, Jim Gettys wrote:
> On 05/07/2012 09:20 PM, Andrew McGregor wrote:
>> Sure... but making the Linux codel ECN capable, and even on by
>> default with no configuration, will have no effect if the clients
>> don't use ECN. So there's no need to even make it optional, let
>> alone default to off.
>>
>>
> The problem is that the client may be managing it's outbound queue with
> codel. So you have to negotiate ECN and if you start marking, you may
> run into trouble.
Are the odds really all that high that when the admin of the client set
tcp_ecn = 1 (or its non-Linux equivalent) that codel running on his
system would be the only thing actually marking and so "the" reason for
trouble? I'm inclined to agree with Andrew. If the client is going to
have trouble with ECN, it will have it once it sets tcp_ecn = 1, codel
being there or not.
rick
next prev parent reply other threads:[~2012-05-08 2:16 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
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 [this message]
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=4FA881F6.9080808@hp.com \
--to=rick.jones2@hp.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