From: Pete Heist <pete@eventide.io>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Tue, 24 Apr 2018 21:10:56 +0200 [thread overview]
Message-ID: <B0A1D004-DFFF-40A8-BC5F-532E2F6CE6AC@eventide.io> (raw)
In-Reply-To: <87k1sw7jxj.fsf@toke.dk>
> On Apr 24, 2018, at 4:34 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Not sure. You do get HOL blocking while a packet is retried, basically.
> And ath9k will keep trying way after it should have given up (up to 30
> retries per packet). If you combine this with a lot of backoff for each
> transmission (which is also quite likely in a very congested setting),
> and I suppose it might be possible…
So that means everyone else waits while a packet is sent and re-sent to a station with a weak signal, for example? I see how that would wreck the latency pretty quick with the number of stations connected, plus channel contention with another repeater. It may be a much bigger factor than bloat.
The physical situation is that there’s an AP on the roof of one cabin, and it’s surrounded by about 8 occupied cabins, each with 4 kids, at least one of which is probably curled up inside using Instagram or YouTube. Signals and tx bitrates of the stations are below, for interest. What I’ll try to find out is if it’s the activities of one or two devices that affect things the most, as it appears that mean latency can suddenly go down to < 10ms and up to > 200ms because of “something"...
root@Cabin_12:~# iw dev ap0_1 station dump | grep "signal avg"
signal avg: -60 [-67, -61] dBm
signal avg: -51 [-58, -52] dBm
signal avg: -61 [-64, -64] dBm
signal avg: -60 [-61, -69] dBm
signal avg: -70 [-72, -73] dBm
signal avg: -70 [-71, -79] dBm
signal avg: -75 [-78, -79] dBm
signal avg: -73 [-79, -76] dBm
signal avg: -75 [-80, -78] dBm
signal avg: -68 [-69, -74] dBm
signal avg: -76 [-77, -86] dBm
signal avg: -84 [-87, -88] dBm
signal avg: -79 [-81, -82] dBm
signal avg: -76 [-81, -78] dBm
signal avg: -58 [-59, -65] dBm
signal avg: -72 [-74, -79] dBm
signal avg: -74 [-81, -75] dBm
signal avg: -80 [-82, -84] dBm
signal avg: -65 [-69, -68] dBm
signal avg: -78 [-81, -81] dBm
signal avg: -68 [-69, -78] dBm
signal avg: -72 [-73, -81] dBm
signal avg: -70 [-76, -71] dBm
signal avg: -80 [-81, -89] dBm
signal avg: -75 [-78, -78] dBm
signal avg: -72 [-76, -74] dBm
signal avg: -78 [-82, -80] dBm
signal avg: -63 [-66, -68] dBm
signal avg: -78 [-85, -79] dBm
signal avg: -75 [-78, -78] dBm
signal avg: -65 [-69, -68] dBm
root@Cabin_12:~# iw dev ap0_1 station dump | grep "tx bitrate"
tx bitrate: 43.3 MBit/s MCS 4 short GI
tx bitrate: 58.5 MBit/s MCS 6
tx bitrate: 57.8 MBit/s MCS 5 short GI
tx bitrate: 72.2 MBit/s MCS 7 short GI
tx bitrate: 52.0 MBit/s MCS 5
tx bitrate: 26.0 MBit/s MCS 3
tx bitrate: 57.8 MBit/s MCS 5 short GI
tx bitrate: 52.0 MBit/s MCS 5
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 19.5 MBit/s MCS 2
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 19.5 MBit/s MCS 2
tx bitrate: 28.9 MBit/s MCS 3 short GI
tx bitrate: 28.9 MBit/s MCS 3 short GI
tx bitrate: 6.5 MBit/s MCS 0
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 58.5 MBit/s MCS 6
tx bitrate: 72.2 MBit/s MCS 7 short GI
tx bitrate: 26.0 MBit/s MCS 3
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 43.3 MBit/s MCS 4 short GI
tx bitrate: 43.3 MBit/s MCS 4 short GI
tx bitrate: 6.5 MBit/s MCS 0
tx bitrate: 28.9 MBit/s MCS 3 short GI
tx bitrate: 1.0 MBit/s
tx bitrate: 6.5 MBit/s MCS 0
tx bitrate: 65.0 MBit/s MCS 7
tx bitrate: 39.0 MBit/s MCS 4
tx bitrate: 26.0 MBit/s MCS 3
tx bitrate: 1.0 MBit/s
next prev parent reply other threads:[~2018-04-24 19:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 8:33 Pete Heist
2018-04-24 11:54 ` Toke Høiland-Jørgensen
2018-04-24 13:37 ` Pete Heist
2018-04-24 13:51 ` Toke Høiland-Jørgensen
2018-04-24 14:09 ` Pete Heist
2018-04-24 14:34 ` Toke Høiland-Jørgensen
2018-04-24 19:10 ` Pete Heist [this message]
2018-04-24 21:32 ` Toke Høiland-Jørgensen
2018-04-25 6:05 ` Pete Heist
2018-04-25 6:36 ` Sebastian Moeller
2018-04-25 17:17 ` Pete Heist
2018-04-26 0:41 ` David Lang
2018-04-26 19:40 ` Pete Heist
2018-04-26 0:38 ` David Lang
2018-04-26 21:41 ` Pete Heist
2018-04-26 21:44 ` Sebastian Moeller
2018-04-26 21:56 ` Pete Heist
2018-04-26 22:04 ` David Lang
2018-04-26 22:47 ` Pete Heist
2018-04-27 10:15 ` Toke Høiland-Jørgensen
2018-04-27 10:32 ` Pete Heist
2018-04-26 0:35 ` David Lang
2018-04-27 11:42 ` Valent Turkovic
2018-04-27 11:50 ` Pete Heist
2018-04-27 11:59 ` Valent Turkovic
2018-04-27 12:17 ` Pete Heist
2018-04-27 11:47 ` Valent Turkovic
2018-04-27 12:00 ` Pete Heist
2018-05-19 16:03 bkil
2018-05-20 18:56 ` Pete Heist
2018-05-31 0:52 ` David Lang
2018-06-08 9:37 ` Pete Heist
2018-06-09 15:32 ` bkil
2018-06-13 13:07 ` Pete Heist
2018-06-13 13:24 ` Toke Høiland-Jørgensen
2018-06-13 16:01 ` Pete Heist
2018-06-30 19:14 ` bkil
2018-07-04 21:47 ` Pete Heist
2018-07-05 13:08 ` Toke Høiland-Jørgensen
2018-07-05 17:26 ` Pete Heist
2018-07-05 17:37 ` Toke Høiland-Jørgensen
2018-07-05 18:02 ` Pete Heist
2018-07-05 20:17 ` Jonathan Morton
2018-07-09 2:20 ` Aaron Wood
2018-07-09 5:17 ` Jonathan Morton
2018-07-09 6:27 ` Pete Heist
2018-07-09 12:55 ` Sebastian Moeller
2018-07-09 23:21 ` Pete Heist
2018-07-09 5:13 ` David Lang
2018-07-09 23:33 ` Pete Heist
2018-07-10 0:39 ` Pete Heist
2018-07-10 7:02 ` bkil
2018-06-13 16:30 ` Sebastian Moeller
2018-06-13 17:50 ` Toke Høiland-Jørgensen
[not found] ` <CADuVhRWL2aVjzjfLHg1nPFa8Ae-hWrGrE7Wga4eUKon3oqoTXA@mail.gmail.com>
2018-06-30 19:26 ` bkil
2018-06-30 20:04 ` Jannie Hanekom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B0A1D004-DFFF-40A8-BC5F-532E2F6CE6AC@eventide.io \
--to=pete@eventide.io \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox