From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (lang.hm [66.167.227.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 367453BA8E for ; Wed, 25 Apr 2018 20:41:18 -0400 (EDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id w3Q0fF5n026245; Wed, 25 Apr 2018 17:41:15 -0700 Date: Wed, 25 Apr 2018 17:41:15 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Pete Heist cc: =?ISO-8859-15?Q?Toke_H=F8iland-J=F8rgensen?= , make-wifi-fast@lists.bufferbloat.net In-Reply-To: <2CD4BD56-8529-4134-8702-B6B89C9ACD91@eventide.io> Message-ID: References: <66BDCA6E-D7C4-4E76-8591-8FDC35B09EA3@eventide.io> <871sf495vs.fsf@toke.dk> <87po2o7lwb.fsf@toke.dk> <1BA3CECA-8C05-4E94-9E2A-1AEA3C2F20B3@eventide.io> <87k1sw7jxj.fsf@toke.dk> <878t9c70jd.fsf@toke.dk> <2CD4BD56-8529-4134-8702-B6B89C9ACD91@eventide.io> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="680960-595449670-1524703275=:12043" Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes 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: Thu, 26 Apr 2018 00:41:18 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --680960-595449670-1524703275=:12043 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Wed, 25 Apr 2018, Pete Heist wrote: >> On Apr 24, 2018, at 11:32 PM, Toke Høiland-Jørgensen wrote: >> >> Yeah, with those signal rates, there's going to be quite some pause when >> the slow stations try to transmit something... :/ > > So then, when would bloat actually become a problem on this hardware? In this case, it's unlikely to be a real problem. Bufferbloat happens when you have a high bandwidth connection on one side and a low bandwidth connection on the other side of a router (the bigger the difference, the more likely you are to run into trouble) In this case, the wifi issues overwelm everything else, and bufferbloat just isn't a noticable --680960-595449670-1524703275=:12043--