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 7D09920016F
	for <bloat@lists.bufferbloat.net>; Thu, 23 Jun 2011 15:10:41 -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 p5NMcCPw027469
	; Fri, 24 Jun 2011 00:38:12 +0200 (CEST)
X-Ids: 164
Received: from lanthane.pps.jussieu.fr (lanthane.pps.jussieu.fr
	[134.157.168.57])
	by hydrogene.pps.jussieu.fr (Postfix) with ESMTPS id 0B6F5C36C1;
	Fri, 24 Jun 2011 00:38:11 +0200 (CEST)
Received: from jch by lanthane.pps.jussieu.fr with local (Exim 4.76)
	(envelope-from <jch@pps.jussieu.fr>)
	id 1QZsXK-00026b-ST; Fri, 24 Jun 2011 00:38:10 +0200
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Dave Taht <dave.taht@gmail.com>
References: <BANLkTimU=0U_L-jKvcszQzJ7tgyif5j+BA@mail.gmail.com>
	<1307537773.3057.17.camel@edumazet-laptop>
	<BANLkTimJSzGJ4z5iseKt0KUsx8CKXJi16g@mail.gmail.com>
	<BANLkTi=3yi4Wtu4+qsmf=YbPL4fZKf_gQQ@mail.gmail.com>
	<1307545032.3057.45.camel@edumazet-laptop>
	<BANLkTimL=eLGgE_R0DUx1USoxC=uMmtUkQ@mail.gmail.com>
Date: Fri, 24 Jun 2011 00:38:10 +0200
In-Reply-To: <BANLkTimL=eLGgE_R0DUx1USoxC=uMmtUkQ@mail.gmail.com> (Dave Taht's
	message of "Wed, 8 Jun 2011 09:20:47 -0600")
Message-ID: <7ivcvwuqb1.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 4E03C054.000 by Joe's j-chkmail
	(http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4E03C054.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] Notes about 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:10:41 -0000

> I will also attempt to argue persuasively that having ECN packet marking in HTB

I'm not following you.  You can only perform ECN marking when you detect
congestion; and you can only detect congestion if you're queueing.
I may be wrong, but I believe that HTB doesn't do any queueing itself,
it delegates queuing to its child qdiscs; hence, I don't see how you can
perform ECN marking in HTB itself; you should be doing it in HTB's child
qdisc.

> RED has it's own idea as to the 'bandwidth' available, and does not
> understand what it's getting has already been shaped by HTB.

I'm not sure I understand that.

-- Juliusz