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 21B8F3BA8E for ; Tue, 27 Nov 2018 16:05:33 -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=1543352731; bh=c9IE0Smoiq7TYgsmtyjxWsF+InmRv1MEzp/zyGqVMRw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=L3y3T7L00unsbcbGkWT2zsYEWbZAWwP9BGPHpFHriwypbIPKSa70Kx4VsiP9IM9RG TWqHF5mmZKPtgrqdALF9H7auSMDZv3fWZt3tTiq+/eTzay80ZI/2NIfDgsvA+zT6XL Nmr7mr+N1dVUmaB8cYQsabKL7CT/M3akQw2e1bbHvMBYEAuOoaLflUiC2e53G5ZkdG RgahLjfc1KGD81Fpi5+Yp3V7wAoWk7FNNuncoa89JIXkg1NipHnO7ovLA1CArno6I8 79cRfONUCydC9+Ac9G9KsLtBVS2rcNxbBqHb4SxmhjhnOsU1/FAUK2eKKsPbBR5R5D EYLiqLSz7RRTA== To: Dave Taht Cc: Neal Cardwell , bloat In-Reply-To: References: <65EAC6C1-4688-46B6-A575-A6C7F2C066C5@heistp.net> <874lc2w89s.fsf@toke.dk> Date: Tue, 27 Nov 2018 22:05:31 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87y39eut7o.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 21:05:33 -0000 Dave Taht writes: > On Tue, Nov 27, 2018 at 12:54 PM Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> >> 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 :) > > Your queue overfloweth. And as good as you are at FQ-ing yourself, I > so dearly would like the !@#!@#@! wifi patches to land in 4.20. Well, 4.20 is already in RC, so that is not going to happen ;) -Toke