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 9837A3BA8E for ; Tue, 5 Jun 2018 18:31:19 -0400 (EDT) Date: Wed, 06 Jun 2018 00:31:17 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1528237878; bh=xZh00SXOv8vdOKtzaRmo9R/peS/2izgsliUk21ZxVoA=; h=Date:In-Reply-To:References:Subject:To:CC:From:From; b=qG/JtWwj+eSAzEdsjXP+MDwhTHiG7th4OukToUYMLQrMidqsHrOeh4CLMpQ8YWi6m nVLKCLUKsVCnWsK8cdyXwin7hCyRnI045ZmLK8IPC/K55eN1KNv243Ywxjd3D89prW zrmMBqiLDfAG82Jhv/nM5M4FNNEejosBzPZfJuLCXb6i5bMucj0jnfxiV8lwvb3u6n hhZ1rrSM2T4VhQWBUlIQzou/u/kha7nEa871XiQwB7BFUSLs84X23NfmzEwfyMHqj9 56tr+Ch4haDQzY7CL5Co2NrUNrDha0kT/2+9ooczwSJhdTIXto2gyg5rygUNFZf5Lv MF9qsELdWNn7w== In-Reply-To: References: <87y3fsevrv.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Dave Taht CC: Make-Wifi-fast From: =?ISO-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= X-Clacks-Overhead: GNU Terry Pratchett Message-ID: Subject: Re: [Make-wifi-fast] I have no idea how this got published... 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: Tue, 05 Jun 2018 22:31:19 -0000 Whaddyamean correct? They don't actually test against our work, if that's w= hat you mean=2E=2E=2E On 6 June 2018 00:23:02 CEST, Dave Taht wrote: >well, are the results correct? > >On Tue, Jun 5, 2018 at 3:03 PM, Toke H=C3=B8iland-J=C3=B8rgensen >wrote: >> https://ieeexplore=2Eieee=2Eorg/stamp/stamp=2Ejsp?arnumber=3D8359288 >> >> They change buffer sizes (but dynamically!) and manage to do better >than >> Linux with CoDel and PIE as qdiscs on the WiFi interface=2E Linux >3=2E17=2E7, >> that is=2E This was published today=2E=2E=2E >> >> What's worse is that they actually cite our paper, with this comment: >> >>> Recently, H=C3=B8iland-J=C3=B8rgensen et al=2E [20] also tackled buffe= rbloat in >>> APs with the goal to reduce latency and improve airtime fairness=2E >>> Their proposal was built on top of FQ-CoDel which is one of the >>> queuing disciplines in Linux=2E We believe that the mesh environment >>> imposes further challenges that are not addressed in this work=2E >> >> I am mildly outraged=2E=2E=2E >> >> -Toke >> _______________________________________________ >> Make-wifi-fast mailing list >> Make-wifi-fast@lists=2Ebufferbloat=2Enet >> https://lists=2Ebufferbloat=2Enet/listinfo/make-wifi-fast