General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Some updates on hacking on AQMS
Date: Thu, 23 Jun 2011 17:10:25 -0600	[thread overview]
Message-ID: <BANLkTikBWYhXHuAmHBqLg5nZ5TyJEh0NQA@mail.gmail.com> (raw)
In-Reply-To: <7ir56kupy8.fsf@lanthane.pps.jussieu.fr>

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..

>
> -- Juliusz
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

  reply	other threads:[~2011-06-23 22:42 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 [this message]
2011-06-24  5:01     ` Eric Dumazet
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=BANLkTikBWYhXHuAmHBqLg5nZ5TyJEh0NQA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jch@pps.jussieu.fr \
    /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