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 41DC33B29E for ; Tue, 24 Apr 2018 09:51:35 -0400 (EDT) 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=1524577894; bh=cwV175OXYO1N3r6QyAnVcurvqKndCGrJwKGZie/NcRc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Wz0uzb6KXhVIZXgP0lTTLL7ppfJhgvLiH67wkXYsWOgIAaw2S0sDrLlrPAhM/aydp XqlGyaJa6wcAGgz2kMNiGNSxgCA7eF3T/ovAB1RetOGDBuXIj/q3k2C1gqwqtes+/+ E0/CiFkT9IP//JsrXSrIO0FbxUveTN61R8GIOZpjEC8UMWpQFVQj1/mSZH07kIiaUx F7kc6hdnBj0u2J8STPHKD/z9GEbgrQAjUWch5NDhlGsenBBM8KzE/2RfNLSBBqUoIU fH9OAuo7Z0n8yEouPNEUsVmFRzSGZA33ReffrSbY7R5EoLS3nMaBtiFvWKu5e2C53m 2vf2IcgCxs7Fg== To: Pete Heist Cc: make-wifi-fast@lists.bufferbloat.net In-Reply-To: References: <66BDCA6E-D7C4-4E76-8591-8FDC35B09EA3@eventide.io> <871sf495vs.fsf@toke.dk> Date: Tue, 24 Apr 2018 15:51:32 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87po2o7lwb.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Tue, 24 Apr 2018 13:51:35 -0000 Pete Heist writes: >> On Apr 24, 2018, at 1:54 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> Pete Heist > writes: >>=20 >>> Mean ping time for >>> cabin 12 is around 200 ms during =E2=80=9Cactive use=E2=80=9D, with out= liers above 1 >>> second, which is higher than expected. I don=E2=80=99t have data collec= ted on >>> how many active users that is and what they=E2=80=99re doing, but there= could >>> be 40-50 students around the cabin 12 AP, with however many active "as >>> is typical for kids=E2=80=9D. >>=20 >> Hmm, yeah, 200ms seems quite high. Are there excessive collisions and >> retransmissions? > > Hrm, how would I know that actually? /proc/net/wireless has all zeroes > in it. I don=E2=80=99t see it anywhere in output from =E2=80=98iw=E2=80= =99... Assuming you have debugfs enabled you should be able to get aggregate statistics from /sys/kernel/debug/ieee80211/phy0/ath9k/xmit - at least that contains retries, but not backoff data, unfortunately. There's also the per-station rate data in /sys/kernel/debug/ieee80211/phy0/= netdev\:*/stations/*/rc_stats >> Is the uplink on the same frequency as the clients? > > Most definitely, the OM2P-HS is a single channel (2.4 GHz) device, > with dual antennas. I was hoping the new driver could make the best of > this situation. :) Well, in that situation 'the best' may not be terribly good ;) > Now, my ping test goes from the gateway straight to the repeater, so > there=E2=80=99s only one WiFi hop in my ping results. I don=E2=80=99t kno= w how pings > actually look for clients while the AP is under load. I suppose I=E2=80= =99ll > either have to test that manually when I=E2=80=99m on site, or set up a f= ixed > wireless SmokePing instance to simulate a client. > > I wish I could cable everything, but it isn=E2=80=99t physically practica= l. > The next possibility is dual channel APs, or separate backhaul links, > all costing something... Yeah, a separate backhaul on a different channel would cut you contention in half, basically. Right now, each transmission has to occupy the channel twice... -Toke