From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F037F3CB36 for ; Tue, 27 Nov 2018 06:52:06 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1543319525; bh=6UevEh/du3R/eJEc10a6qRhwjtSzdaCrgPVz/V2d7T8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=NSErTXvfe7KP9ADnYIDur8pF+Vfe9JuhqvBKcRZ3C5j+ZNA64kmv9l9cUN/fxGoTb yZwulFZFFyz2i0gYv5g2R3dh9wMFwUEj70R+HNjdsJKhdtezUruVwdASSkFC9DytQK vCvL3YKq3aQ4NPSyCypM3ycK49qg0fAYVoIdyDsVAk7qHaPLXfoUJMgKj7tu7GMiGL thmV1iVxpbZxp5NLNMD7dt87sXGaYPW9ah25Nd4uel3ceENOOG7HHsoDzgMUX4idBU mXTK8rHW+ulP9tm85qTArw+0lzRYN7LwHxCy2ZDHTJ3+UJWjK5nB/ynaF5rXrIbTo8 p+IqUBQwGqG0w== To: Luca Muscariello , Jonathan Morton Cc: bloat In-Reply-To: References: <65EAC6C1-4688-46B6-A575-A6C7F2C066C5@heistp.net> Date: Tue, 27 Nov 2018 12:52:05 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <877egyspp6.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] when does the CoDel part of fq_codel help in the real world? 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: Tue, 27 Nov 2018 11:52:07 -0000 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? -Toke