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 63DAC3B29E; Fri, 1 Dec 2017 07:53:56 -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=1512132833; bh=lwqrxz5BiX+MlwiBvOC2kr40jj14XEsb68ks0Znx8Lg=; h=From:To:Subject:In-Reply-To:References:Date:From; b=UZ08u0jHCg1B71TbesLFj1dfo8PHMZDNzlAE2yz/rmiUAjHMhbjhWJinou+TCeHpX l9RCxxz6q8EwIWPFR7etnYwSHckXhHcpW2aRg/GHh8wMbS2Zo2cj9j2/ZTm+CrKJmf 1CmSvpJUIzKcn9QZnImfOoxWxfjB7PuKMukkV8OJiNb434yYjN1CifKb+IfmulyTxQ 9SEfuGd69cCpmZH2vrefcf/8Ra38Y4isWoV3884RJVn+WEp+37u+4aVill6Zlwue3D 1idXs1e0XtfPIj1WwU0OvsGS9hTi1EO1+COUvL6vflKFw3XUdz7xDs1a57wcKuvqIE JjS/JrV+CatSg== To: Jan Ceuleers , bloat@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net In-Reply-To: <6b494910-1373-afb0-5b93-99b725391fb3@gmail.com> References: <4D0E907C-E15D-437C-B6F7-FF348346D615@gmx.de> <7B92DF4D-B6B5-4A64-9E10-119DCA2D4A6F@ifi.uio.no> <1512037480.19682.10.camel@gmail.com> <6b494910-1373-afb0-5b93-99b725391fb3@gmail.com> Date: Fri, 01 Dec 2017 13:53:51 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87wp2638yo.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] [Bloat] benefits of ack filtering X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 12:53:56 -0000 Jan Ceuleers writes: > On 01/12/17 01:28, David Lang wrote: >> Stop thinking in terms of single-flow benchmarks and near idle >> 'upstream' paths. > > Nobody has said it so I will: on wifi-connected endpoints the upstream > acks also compete for airtime with the downstream flow. There's a related discussion going on over on the make-wifi-fast list related to the FastACK scheme proposed by Meraki at this year's IMC: https://conferences.sigcomm.org/imc/2017/papers/imc17-final203.pdf It basically turns link-layer ACKs into upstream TCP ACKs (and handles some of the corner cases resulting from this) and also seems to contain an ACK compression component. -Toke