Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Tim Higgins <tim@smallnetbuilder.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Fun with DSCP and latency
Date: Thu, 21 Jan 2021 23:04:36 -0800	[thread overview]
Message-ID: <CAHb6Lvpt441LjsKV-sKbcZoDTAy=PxrzcCQKp6Pj-nkm5wi1fg@mail.gmail.com> (raw)
In-Reply-To: <a4e1ca0f-fb19-de2e-c9e5-c3277fe27ee0@smallnetbuilder.com>


[-- Attachment #1.1: Type: text/plain, Size: 2392 bytes --]

I can't speak to these chips or drivers but we have the ability to fault
isolate latency via much more advanced network telemetry.

This type of testing seems likely to be conflating buffer bloat with
latency. They're two different phenomena.

iperf 2.1.0 <https://sourceforge.net/projects/iperf2/> has a
--near-congestion option to help test latency rather than bloat. It's not
perfect but is reproducible for controlled networks.

Also, probably a good idea to synchronize clocks.  NTP stratum-1 servers
can be built with a raspberry pi and a GPS hat. One can yse PTP to
distribute.

The average crystal ends up being about as accurate as a mechanical watch
<https://tinyurl.com/y3jbwgmy>
DIY Raspberry Pi GPS stratum 1 clock
<https://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html>

Bob

On Thu, Jan 21, 2021 at 1:09 PM Tim Higgins via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:

> Hi all,
>
> I've found unexpected behavior running simultaneous ping and TCP/IP tests
> using multiple AX200
> based Linux STAs and different iperf3 --dscp values for each STApal.
>
> Details are in the document linked below. I'd appreciate it if you could
> read and comment.
>
> _
> https://docs.google.com/document/d/1XB-DaqBzDDprdb-SorWK5sSwtzMhrOSYXiDOrGU_fq4/edit?usp=sharing_
> <
> https://docs.google.com/document/d/1XB-DaqBzDDprdb-SorWK5sSwtzMhrOSYXiDOrGU_fq4/edit?usp=sharing
> >
>
> Thanks
> ===========
> Tim Higgins
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

-- 
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: 3394 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4163 bytes --]

      reply	other threads:[~2021-01-22  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 21:08 Tim Higgins
2021-01-22  7:04 ` 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='CAHb6Lvpt441LjsKV-sKbcZoDTAy=PxrzcCQKp6Pj-nkm5wi1fg@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=tim@smallnetbuilder.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