From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jch@pps.jussieu.fr>
Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 3F390200686
	for <bloat@lists.bufferbloat.net>; Thu, 23 Jun 2011 15:18:44 -0700 (PDT)
Received: from hydrogene.pps.jussieu.fr (hydrogene.pps.jussieu.fr
	[134.157.168.1])
	by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p5NMjqQE091258
	; Fri, 24 Jun 2011 00:46:05 +0200 (CEST)
X-Ids: 165
Received: from lanthane.pps.jussieu.fr (lanthane.pps.jussieu.fr
	[134.157.168.57])
	by hydrogene.pps.jussieu.fr (Postfix) with ESMTPS id 55F6FC36C1;
	Fri, 24 Jun 2011 00:45:51 +0200 (CEST)
Received: from jch by lanthane.pps.jussieu.fr with local (Exim 4.76)
	(envelope-from <jch@pps.jussieu.fr>)
	id 1QZsel-00026f-6Y; Fri, 24 Jun 2011 00:45:51 +0200
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Dave Taht <dave.taht@gmail.com>
References: <BANLkTimWZDPkycYcAtfMVsZitwcC2itqVQ@mail.gmail.com>
Date: Fri, 24 Jun 2011 00:45:51 +0200
In-Reply-To: <BANLkTimWZDPkycYcAtfMVsZitwcC2itqVQ@mail.gmail.com> (Dave Taht's
	message of "Thu, 9 Jun 2011 08:01:26 -0600")
Message-ID: <7ir56kupy8.fsf@lanthane.pps.jussieu.fr>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Miltered: at jchkmail.jussieu.fr with ID 4E03C220.000 by Joe's j-chkmail
	(http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4E03C220.000/134.157.168.1/hydrogene.pps.jussieu.fr/hydrogene.pps.jussieu.fr/<jch@pps.jussieu.fr>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Some updates on hacking on AQMS
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 22:18:44 -0000

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

-- Juliusz