From: Dave Taht <dave@taht.net>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi
Date: Sun, 26 Nov 2017 15:11:55 -0800 [thread overview]
Message-ID: <877eucr5xg.fsf@nemesis.taht.net> (raw)
In-Reply-To: <ad112e0e-edb8-96dc-00b3-76bbd77d2c2b@gmail.com> (Jan Ceuleers's message of "Sun, 26 Nov 2017 19:43:41 +0100")
Jan Ceuleers <jan.ceuleers@gmail.com> writes:
> Resending with the from-address with which I'm subscribed to the list
>
> On 26/11/17 18:53, Dave Taht wrote:
>> On Sun, Nov 26, 2017 at 2:05 AM, Jonathan Morton <chromatix99@gmail.com> 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.
>>
>> I'd written that up here:
>>
>> http://blog.cerowrt.org/post/disabling_channel_scans/
>>
>> Which was improved in some release of network manager
>>
>> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/373680
>
> Dave,
>
> Thanks, but that's not the same problem I experienced. Yours was
> entirely client-side (i.e. it was behaviour of Network Manager). My
> problem was due to the AP asking the client to periodically perform
> scans (by means of hostapd's obss_interval parameter).
Got it. Thanks!
>
> Similar (but not the same) symptoms - different cause.
>
> Jan
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2017-11-26 23:11 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
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 [this message]
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=877eucr5xg.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=jan.ceuleers@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