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 DF1753CB40 for ; Fri, 19 Jan 2018 04:58:52 -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=1516355921; bh=SwvsIA14mnLrs6ap3gmjfk0iyFZmomBYP/Xpqiz7eL8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=NAv62mCu0Z7D50DOhilcSE4YrBVKMeqN74qG5bcaJbgZFlJ1V4/q6WA0eTb2p3oA7 CoeQ+w+WmyMqezccMkn9t1LqxZ/5mRXCTZltT0CPHy3kXat6v5XEEplpchJwa3Ut7P FlPwfBsl51jKC1k2Tx2E6f0L78sh0JUZOa2gHmXLRd1KDm/uGBfLDwYhO5K/VMjxUi 8/KNwx22oLqd3Ac6RsMBqZ3iz46WxUn3P+9fN1l1M3Dfvx3nmKY67s8E07HwnzwghB Q6L0GzGtqwqs+nT8sL3RYHZqN9HNNRuio124SyQ54A3wabY45B3QTgNcNXdiusn8oz H9Q/Bfpg9kToA== To: David Lang , make-wifi-fast@lists.bufferbloat.net In-Reply-To: <87efmovk00.fsf@toke.dk> References: <87efmovk00.fsf@toke.dk> Date: Fri, 19 Jan 2018 10:58:49 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87po66tbja.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Fri, 19 Jan 2018 09:58:53 -0000 Toke H=C3=B8iland-J=C3=B8rgensen 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=3D2999572.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