From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi
Date: Sun, 26 Nov 2017 11:53:04 +0100 [thread overview]
Message-ID: <ca0cc7d1-9cfc-ec97-a3eb-3df930f9f4e5@gmail.com> (raw)
In-Reply-To: <CAJq5cE1OZOUGM2rKT1K5yN9gtT-+mHRFxTUA5C05UqcoJki1QA@mail.gmail.com>
On 26/11/17 11:05, Jonathan Morton wrote:
> Another explanation for latency spikes on the order of 100ms is that a
> periodic (and wholly unnecessary) scan for other APs is run, which
> requires the wifi radio to be temporarily tuned away from the currently
> associated AP's frequency.
My understanding is that APs that operate on channels that are wider
than 20MHz must back off to 20MHz in case they detect other SSIDs that
are competing for the wider channel. So this is clearly "unnecessary"
from the point of view of the AP itself, but it does make the AP a
better citizen to be aware of who else is trying to access the medium.
next prev parent reply other threads:[~2017-11-26 10:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 19:08 Hal Murray
2017-11-22 10:31 ` Neil Davies
2017-11-23 17:48 ` Caleb Cushing
2017-11-24 9:20 ` Hal Murray
2017-11-24 9:34 ` Neil Davies
2017-11-26 7:25 ` Caleb Cushing
2017-11-26 7:29 ` Caleb Cushing
2017-11-26 7:55 ` Jan Ceuleers
2017-11-26 10:05 ` Jonathan Morton
2017-11-26 10:53 ` Jan Ceuleers [this message]
2017-11-26 10:55 ` Jonathan Morton
2017-11-26 11:54 ` Steinar H. Gunderson
2017-11-26 13:03 ` Jan Ceuleers
2017-11-26 13:05 ` Jan Ceuleers
2017-11-26 13:13 ` Steinar H. Gunderson
2017-11-26 17:53 ` Dave Taht
2017-11-26 18:43 ` Jan Ceuleers
2017-11-26 23:11 ` Dave Taht
2017-12-04 7:24 ` Caleb Cushing
-- strict thread matches above, loose matches on Subject: below --
2017-11-18 22:14 Caleb Cushing
2017-11-19 16:28 ` Toke Høiland-Jørgensen
2017-11-19 21:18 ` Caleb Cushing
2017-11-19 21:27 ` Toke Høiland-Jørgensen
2017-11-19 22:03 ` Caleb Cushing
2017-11-19 22:13 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca0cc7d1-9cfc-ec97-a3eb-3df930f9f4e5@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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