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 4E24E3BA8E for ; Tue, 27 Nov 2018 22:37:52 -0500 (EST) Received: from dancer.taht.net (unknown [IPv6:2603:3024:1536:86f0:eea8:6bff:fefe:9a2]) (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 9E4B221455; Wed, 28 Nov 2018 03:37:50 +0000 (UTC) From: Dave Taht To: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= Cc: Luca Muscariello , Jonathan Morton , bloat References: <65EAC6C1-4688-46B6-A575-A6C7F2C066C5@heistp.net> <877egyspp6.fsf@toke.dk> Date: Tue, 27 Nov 2018 19:37:39 -0800 In-Reply-To: <877egyspp6.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Tue, 27 Nov 2018 12:52:05 +0100") Message-ID: <875zwh3m9o.fsf_-_@taht.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: [Bloat] AFD X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2018 03:37:52 -0000 Toke H=C3=B8iland-J=C3=B8rgensen writes: > Luca Muscariello writes: > >> This procedure would allow to size FQ_codel but also SFQ. >> It would be interesting to compare the two under this buffer sizing. >> It would also be interesting to compare another mechanism that we have >> mentioned during the defense >> which is AFD + a sparse flow queue. Which is, BTW, already available in >> Cisco nexus switches for data centres. > > One think I wondered about afterwards was whether or not it would be > feasible (as in, easy to add, or maybe even supported in current > versions) to tie in an AQM to an AFD-type virtual fairness queueing > system? You could keep the AQM state variables along with the per-flow > state and react appropriately. Any reason why this wouldn't work? Just bookmarking this thought for now.