From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Michael Yartys <michael.yartys@protonmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Weird periodic latency
Date: Sat, 16 Jan 2021 13:01:16 -0800 [thread overview]
Message-ID: <CAHb6LvpPE+WOrjG5CuhbCS6B2evOuEJ_R0ajJfPF8NOevtrxxA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6bkWN-0eSCF5+x29x7sfTRyvfUAjMTXk9FHB_s8cZHFA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2636 bytes --]
I think more current WiFi chips can do scanning without any impact to
traffic per having dedicated radios for off channel
estimates. Also, it's good to know the width of the latency impacts along
with the delay values. Finally, fault isolation
could include a UDP send with the ack as shown here
<https://www.spinics.net/lists/netdev/msg176415.html>. We find ping
latencies, though a widely available tool, as insufficient
to qualify or diagnose latency.
Bob
On Sat, Jan 16, 2021 at 9:48 AM Dave Taht <dave.taht@gmail.com> wrote:
> That implies it is doing a channel scan. Dumb.
>
> https://blog.cerowrt.org/post/disabling_channel_scans/
>
> but what you encountered seemed more disabling than that, and the
> ath10k is supposed to be able to do background channel scans.
>
>
> On Sat, Jan 16, 2021 at 6:47 AM Michael Yartys
> <michael.yartys@protonmail.com> wrote:
> >
> > I'm pretty sure I've managed to figure out what causes the short sharp
> periodic latency spikes. The Gnome location service uses the surrounding
> wireless networks as one of the methods to determine your location. When
> it's turned on I get the following results:
> >
> > https://imgur.com/a/pNXuVRe
> >
> > When it's disabled the latency spikes are gone (and notice that AQL is
> working here as there is some background traffic from other clients):
> >
> > https://imgur.com/a/v4wWkAC
> >
> > Now, I wasn't able to reproduce the weird roller coaster like latency
> that I saw previously. I rebooted the laptop before I did these tests, so I
> guess that solved it.
> >
> > Michael
>
>
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 3514 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4163 bytes --]
prev parent reply other threads:[~2021-01-16 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 16:02 Michael Yartys
2021-01-15 16:23 ` Toke Høiland-Jørgensen
2021-01-15 16:59 ` Michael Yartys
2021-01-15 18:55 ` Toke Høiland-Jørgensen
2021-01-15 19:22 ` Michael Yartys
2021-01-15 19:28 ` Toke Høiland-Jørgensen
[not found] ` <CAA93jw6uLUC9b-vuPrEcL_VqXWPOtqUo=ek2G0x=XmvJ-GfLKw@mail.gmail.com>
2021-01-15 19:10 ` Dave Taht
2021-01-15 19:33 ` Michael Yartys
2021-01-15 21:44 ` Bob McMahon
2021-01-16 14:46 ` Michael Yartys
2021-01-16 17:48 ` Dave Taht
2021-01-16 18:01 ` Michael Yartys
2021-01-16 18:06 ` Dave Taht
2021-01-16 18:14 ` Michael Yartys
2021-01-16 18:20 ` Dave Taht
2021-01-16 21:01 ` Bob McMahon [this message]
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=CAHb6LvpPE+WOrjG5CuhbCS6B2evOuEJ_R0ajJfPF8NOevtrxxA@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.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