From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4859F3BA8E; Fri, 3 Nov 2017 14:59:08 -0400 (EDT) Received: from nemesis.taht.net (unknown [IPv6:2603:3024:1536:86f0:2e0:4cff:fec1:1206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 8852C21341; Fri, 3 Nov 2017 18:59:06 +0000 (UTC) From: Dave Taht To: Rich Brown Cc: bloat , cake@lists.bufferbloat.net References: Date: Fri, 03 Nov 2017 11:59:04 -0700 In-Reply-To: (Rich Brown's message of "Fri, 3 Nov 2017 10:53:57 -0400") Message-ID: <878tfnp4sn.fsf@nemesis.taht.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] [Bloat] Update Cake page on bufferbloat.net? X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2017 18:59:08 -0000 Rich Brown writes: > Hi folks, > > I saw a blog posting that was enthusing about codel/fq_codel, and I was moved to > respond that the state of the art was now cake. where? > But I looked at the Cake page on Bufferbloat.net and wonder if everything there > is true, or whether it would be good to update > it. https://www.bufferbloat.net/projects/codel/wiki/Cake/ It's pretty much true. > (Once the technical information on that page is current, I would also be willing > to tackle a modest reorganization to add some background info to the beginning > so that we can cite that page as the primary reference for Cake.) I would really for us to make the effort to upstream this in 2018. I'm still dubious about "cobalt", and I'd like to make the GRO peeling less agressive (again), relative to load, and it needs some cleanups to match current kernels. > > Thanks! > > Rich > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat