CoDel AQM discussions
 help / color / mirror / Atom feed
From: "Richard Scheffenegger" <rscheff@gmx.at>
To: "Eric Dumazet" <eric.dumazet@gmail.com>,
	"Andrew McGregor" <andrewmcgr@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] [RFC PATCH] codel: ecn mark at target
Date: Sun, 5 Aug 2012 18:54:34 +0200	[thread overview]
Message-ID: <4A256974B5054317913BC067C4E5FAE1@srichardlxp2> (raw)
In-Reply-To: <1344144623.9299.1557.camel@edumazet-glaptop>

Hi Eric,

----- Original Message ----- 
From: "Eric Dumazet" <eric.dumazet@gmail.com>
To: "Andrew McGregor" <andrewmcgr@gmail.com>
Cc: <codel@lists.bufferbloat.net>
Sent: Sunday, August 05, 2012 7:30 AM
Subject: Re: [Codel] [RFC PATCH] codel: ecn mark at target


> On Sat, 2012-08-04 at 20:06 -0700, Andrew McGregor wrote:
>> Well, thanks Eric for trying it.
>>
>> Hmm.  How was I that wrong?  Because I was supporting that idea.
>>
>> Time to think.
>
> No problem Andrew ;)
>
> Its seems ECN is not well enough understood.
>
> ECN marking a packet has the same effect for the sender : reducing cwnd
> exactly like a packet drop. Only difference is avoiding the
> retransmit[s].

That's true for the first mark; any subsequent mark (during the same window) 
should have no effect - thus a high marking rate (marking fraction per 
window) should not be that much worse... Of course, the queue can never know 
the effective window of the tcp stream it is marking...

As a test, when the marking is done really instead of drop, do you see 
fairness betwenn the ecn and legacy tcp flows? (if not, the ecn 
implementation may be faulty).

>
> It cannot be used only to send a 'small' warning, while other competing
> non ECN flows have no signal.
>
> As far as packet schedulers are concerned, there should be no difference
> in ECN marking and dropping a packet. I believe linux packet schedulers
> are fine in this area.
>
> Now, there are fundamental issues with ECN itself, out of Codel scope,
> thats for sure.
>
> How widely has been RFC 3540 deployed, anybody knows ?

Virtually not; even if the end hosts negotiate ECN, the network doesn't do 
any marking (rendering ecn mood).

See
Bauer and Beverly, "Measuring the current state of ECN support in server, 
clients, and routers",

http://mirrors.bufferbloat.net/Talks/AIMS2011/bauer-ecn-aims-2011.pdf


>
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel 


  parent reply	other threads:[~2012-08-05 17:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04  2:44 Dave Täht
2012-08-04  6:45 ` Eric Dumazet
2012-08-04 21:53   ` Kathleen Nichols
2012-08-05  3:06     ` Andrew McGregor
2012-08-05  5:30       ` Eric Dumazet
2012-08-05 16:53         ` Andrew McGregor
2012-08-05 16:58           ` Kathleen Nichols
2012-08-05 17:14             ` Andrew McGregor
2012-08-05 17:15           ` Eric Dumazet
2012-08-05 16:54         ` Richard Scheffenegger [this message]
2012-08-05 17:25           ` Eric Dumazet
2012-08-05 17:35             ` Eric Dumazet
2012-08-05 18:14               ` Yuchung Cheng
2012-08-05 18:40                 ` Eric Dumazet
2012-08-05 19:49                   ` Eric Dumazet
2012-08-06 16:22                   ` Richard Scheffenegger
2012-08-06 16:46                     ` Eric Dumazet
2012-08-06 17:50                       ` Dave Taht
2012-08-06 19:09                         ` Andrew McGregor
2012-08-06 20:01                           ` Eric Dumazet
2012-08-10 17:48                             ` Dave Taht
2012-08-04  7:00 ` Roger Jørgensen
2012-08-04 13:38   ` Richard Scheffenegger
2012-08-04 17:21     ` Eric Dumazet

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=4A256974B5054317913BC067C4E5FAE1@srichardlxp2 \
    --to=rscheff@gmx.at \
    --cc=andrewmcgr@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --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