From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F0A693BA8E for ; Tue, 27 Nov 2018 15:54:57 -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=1543352096; bh=ILU73KtOcqkYYkd/Ryt9EbDSD6yi0w4d8wzszUPdzV8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ej9hU4q8wuujJbT1M0UGWL9n7TqhVOV9U4gZ5DxtXmjG00EBMjaXZ1UKSI9Tom5uH pmZJ1fQ63igJdKqq8yXIwxR2O8uTpDrLBuASbfIUaMzaK0eyLxIIcClJ42397tnyLy NJzseyamSOx5q5dHV5Z3MMIV+zsqWupEBmcGV+CoLMI90PYUfCaEWC+7PC63ZlS+/s 2cpquKL/i7N/2uQyKr8kZZO4KlXX/JSr9Pq+pQfcF/vvEPXufD7wh2WXyaNicEWep2 Wsy+nPJf5G0u+rBabyDMdNDrLryvneKg9tIg6+c80b3zGzUPKBm+aZ+7a+nj9C3xqU RelWEoArr5EZQ== To: Dave Taht , Neal Cardwell Cc: bloat In-Reply-To: References: <65EAC6C1-4688-46B6-A575-A6C7F2C066C5@heistp.net> Date: Tue, 27 Nov 2018 21:54:55 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <874lc2w89s.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 20:54:58 -0000 Dave Taht writes: > I've done things like measure induced latency on wireguard streams of > late and codel keeps it sane. still, wireguard internally is optimized > for single flow "dragster" performance, and I'd like it to gain the > same fq_codel optimization that did such nice things for multiple > flows terminating on the router for ipsec. The before/after on that > was marvelous. This is on my list, FWIW :) -Toke