General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Some updates on hacking on AQMS
Date: Fri, 24 Jun 2011 07:01:00 +0200	[thread overview]
Message-ID: <1308891660.3000.7.camel@edumazet-laptop> (raw)
In-Reply-To: <BANLkTikBWYhXHuAmHBqLg5nZ5TyJEh0NQA@mail.gmail.com>

Le jeudi 23 juin 2011 à 17:10 -0600, Dave Taht a écrit :
> On Thu, Jun 23, 2011 at 4:45 PM, Juliusz Chroboczek <jch@pps.jussieu.fr> wrote:
> >> It really seems that ECN support could be added generically for all
> >> qdiscs that currently do packet drop. Creating a generic mark_or_drop
> >> function is easy.
> >
> > As hinted in a previous message -- please don't.  Every qdisc must be
> > examined individually to check if it is suitable for ECN.
> >
> > Consider also the following.  If the administrator specifies a maximum
> > rate of 100 Mbit/s, he probably doesn't expect the outgoing traffic to
> > exceed that rate under any circumstances.  If you start marking instead
> > of dropping, you must make sure that the resulting traffic is still
> > under 100 Mbit/s, including the marked packets.
> 
> In designing this particular concept I made sure that was an option,
> in the mildly recorrected:
> 
> http://www.bufferbloat.net/projects/bloat/wiki/Save_the_Ants
> 
> Try harder to not shoot the ants, but make ecn marking a first class
> option throughout the qdiscs...
> 
> if possible..

I believe it was done.

qdisc implementations are not random, but follow extensive research
works.

Before doing a change like that, you must redo all the experiments and
show the pro/cons ;)

Once qdisc queue is _full_, its too late, you have to drop packets
anyway. And its not because at least one flow is not responsive :
It might be because one thousand flows began their life at the very same
moment :(




  reply	other threads:[~2011-06-24  4:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 14:01 Dave Taht
2011-06-23 22:45 ` Juliusz Chroboczek
2011-06-23 23:10   ` Dave Taht
2011-06-24  5:01     ` Eric Dumazet [this message]
2011-06-24  9:10       ` Dave Taht
2011-06-24 10:03         ` 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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1308891660.3000.7.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.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