CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrew McGregor <andrewmcgr@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] [RFC PATCH] codel: ecn mark at target
Date: Sun, 05 Aug 2012 19:15:08 +0200	[thread overview]
Message-ID: <1344186908.9299.1603.camel@edumazet-glaptop> (raw)
In-Reply-To: <D9F88FED-3D9C-4FA7-89DF-CD312ED7DC31@gmail.com>

As far as CoDel is concerned, we could have two stages of control :

The current one, to mark/drop packet as specified by Kathleen & Van

Then, for marked (ecn) packets, pass a second codel stage, but dropping
packets this time, to make sure we dont allow queue to become too large.


On Sun, 2012-08-05 at 09:53 -0700, Andrew McGregor wrote:
> Well, there's a lot of people at the IETF who really want to do other things with ECN, but it seems like the simple version is far too aggressive.
> 
> So, I think the desirable properties are something like:
> 1) Allow ECN flows to achieve the same or slightly higher throughput to maintain an incentive to deploy it.
> 2) Still drop ECN flows eventually to avoid too much queue buildup.
> 3) Account somehow for the fact that marking takes longer to control the queue (but we don't know how much longer).
> 
> Maybe mark ECN instead of dropping, but if we end up trying to mark/drop twice in one round, drop the later packets?
> 
> Oh, and ECN nonce deployment is negligible, to the extent that there are proposals in the IETF to reuse the bits for other things, and there is no pushback on that.
> 
> Andrew
> 
> On 4/08/2012, at 10:30 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> 
> > 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].
> > 
> > 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 ?
> > 
> > 
> > 
> 



  parent reply	other threads:[~2012-08-05 17:15 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 [this message]
2012-08-05 16:54         ` Richard Scheffenegger
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=1344186908.9299.1603.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=andrewmcgr@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    /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