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 339043B29E for ; Sun, 11 Feb 2018 15:25:53 -0500 (EST) 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 w1BKPodu031628; Sun, 11 Feb 2018 12:25:50 -0800 Date: Sun, 11 Feb 2018 12:25:50 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: =?ISO-8859-15?Q?Toke_H=F8iland-J=F8rgensen?= cc: make-wifi-fast@lists.bufferbloat.net In-Reply-To: <87po66tbja.fsf@toke.dk> Message-ID: References: <87efmovk00.fsf@toke.dk> <87po66tbja.fsf@toke.dk> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="680960-1171388735-1518380750=:31300" Subject: Re: [Make-wifi-fast] what is the state of the airtime fairness patches? 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: Sun, 11 Feb 2018 20:25:53 -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-1171388735-1518380750=:31300 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT Is there any ath10k hardware that is especially recommended? The Scale network is currently all WNDR3800, but we would like to get a handful of -ac routers to see how much of our userbase is using -ac equipment David Lang On Fri, 19 Jan 2018, Toke Høiland-Jørgensen wrote: > Date: Fri, 19 Jan 2018 10:58:49 +0100 > From: Toke Høiland-Jørgensen > To: David Lang , make-wifi-fast@lists.bufferbloat.net > Subject: Re: [Make-wifi-fast] what is the state of the airtime fairness > patches? > > Toke Høiland-Jørgensen writes: > >>> Is there anything you would like me to gather in this environment? >> >> Hmm, things that might be interesting: >> >> - Distribution of client capabilities (5/2.4Ghz, MIMO mode, n/ac, >> achieved rates, etc. - however much data you can reasonably gather) >> >> - Lasthop latency experienced by the clients (you could get this by >> capturing TCP handshakes and measuring the ACK-SYNACK delay, as shown >> in Figure 1 of this paper: >> https://dl.acm.org/citation.cfm?doid=2999572.2999603) - this could >> give an indication of bloat in the client drivers. >> >> - QoS usage (how much traffic is sent on each of the VO/VI/BE/BK >> queues). > > A few more things for the list: > > - The number of stations that have packets queued at the AP over time. > > - Distribution of traffic between protocols (v4/v6, TCP/UDP/others). > > -Toke > --680960-1171388735-1518380750=:31300--