CoDel AQM discussions
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Andrew McGregor <andrewmcgr@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 21:45:32 -0400	[thread overview]
Message-ID: <4FA87ABC.4080907@freedesktop.org> (raw)
In-Reply-To: <A89B0AB0-38A7-4FA8-88B8-83F06CAF5056@gmail.com>

On 05/07/2012 09:20 PM, Andrew McGregor wrote:
> On 8/05/2012, at 1:15 PM, Jim Gettys wrote:
>
>> On 05/07/2012 04:03 PM, Eric Dumazet wrote:
>>> 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.
>> Client initiated ECN may still be problematic.  It is *fine* if a system
>> responds to ECN that is sent to it.  We know that is fine, as Linux has
>> had the server side of ECN enabled for quite a few years, and those
>> systems now are > 20% of servers on the internet.
>>
>>
>> What we don't want is to get a pile of codel bug reports that are really
>> ECN related problems, of which we know there are quite a few.
>>                            - Jim
>>
> 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.
                - Jim


  reply	other threads:[~2012-05-08  1: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
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 [this message]
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=4FA87ABC.4080907@freedesktop.org \
    --to=jg@freedesktop.org \
    --cc=andrewmcgr@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@bufferbloat.net \
    --cc=edumazet@google.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