From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (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 C8D2D21F5BF for ; Tue, 3 Nov 2015 09:54:21 -0800 (PST) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1446573259; bh=atAeBpYH2jiP9n/muZyPkMJD8Ya7derGkK8eBw439sI=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=rNyNTWxG3bVIQqI+gVC7zyoTkeGzUFEFzHcE7YEGlgR+360CRK4MnOd34hinMvu4E GlXJXA+skD09012gXeboEteV13URF194PjgcRUfJBXc1nJ8OREP+tYDPW5s0e19hJB i2zAA14mAN7GpPN/V+3N2QqJMGQZVt2/fPy+DQSE= Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id A79D84E6F1A; Tue, 3 Nov 2015 18:54:18 +0100 (CET) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Moeller References: <87pozspckj.fsf@toke.dk> <6A2609D9-7747-487B-9484-ECC69C50DE96@gmx.de> <874mh3pai9.fsf@toke.dk> <50C2A7B7-1B81-41E1-B534-CA449296FE77@gmail.com> <87a8qvc8tz.fsf@toke.dk> <328DEF4F-F149-42C5-920E-53D16DCF544C@gmx.de> <87si4natbf.fsf@toke.dk> <87fv0nasy5.fsf@toke.dk> <878u6fas88.fsf@toke.dk> <64F71419-78F8-465F-B43E-D0F2CF08AB19@gmx.de> Date: Tue, 03 Nov 2015 18:54:18 +0100 In-Reply-To: <64F71419-78F8-465F-B43E-D0F2CF08AB19@gmx.de> (Sebastian Moeller's message of "Tue, 3 Nov 2015 18:52:51 +0100") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <8737wnarzp.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Cc: cake@lists.bufferbloat.net Subject: Re: [Cake] Long-RTT broken again X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 17:54:22 -0000 Sebastian Moeller writes: > Except, both are strongly correlated in practise, by virtue of each > packet pinning a 2KB skb, I do not care too much if there is a > constant factor required to get from packet limit to memory or not. > What I really want is that halving the limit halves the memory demand > ;). Well, all other things being equal it would either way... :) -Toke