CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, "Dave Täht" <dave.taht@bufferbloat.net>
Subject: Re: [Codel] [RFCv2 PATCH] codel: add ecn_target for when to drop rather than mark ecn packets
Date: Mon, 25 Jun 2012 17:45:51 +0200	[thread overview]
Message-ID: <1340639151.10893.79.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw60d1U+nD0A3e-LrM9rHjBKF340WMZPWM2Yh7DPw9X7eg@mail.gmail.com>

On Mon, 2012-06-25 at 08:30 -0700, Dave Taht wrote:

> It was the way I was leaning until I observed me dropping ecn enabled
> mosh, ssh, and babel packets , which tend to be small, so I started
> thinking in terms of dropping ecn packets on a graduated packet size
> scale after exceeding target. ESPECIALLY in case of overload you want
> command and control packets to get through.
> 

Don't try to add in CoDel things that should be done at another layer.
There is no classification in CoDel : Its a FIFO.

Only way is to prioritize control packets if you need to, and use
several queues.

I dont understand... Are you saying that you feel the need to drop
packets instead of marking them in a 'good citizen world' (none of your
flow pretends to use ECN to avoid drops) ?




  reply	other threads:[~2012-06-25 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  5:00 [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel Dave Täht
2012-06-25  5:00 ` [Codel] [RFCv2 PATCH] codel: add ecn_target for when to drop rather than mark ecn packets Dave Täht
2012-06-25  5:22   ` Eric Dumazet
2012-06-25 14:50     ` Dave Taht
2012-06-25 15:20       ` Eric Dumazet
2012-06-25 15:30         ` Dave Taht
2012-06-25 15:45           ` Eric Dumazet [this message]
2012-06-25 17:48             ` Jonathan Morton
2012-06-25 18:25               ` Dave Taht
2012-06-25 18:51                 ` Eric Dumazet
2012-06-25  5:24 ` [Codel] [RFCv2 PATCH] iproute2: Add ecn_target option to codel and fq_codel Eric Dumazet
2012-06-25  5:29 ` Eric Dumazet
2012-06-25 14:54   ` Dave Taht

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=1340639151.10893.79.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@bufferbloat.net \
    --cc=dave.taht@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