Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Cc: Vint Cerf <vint@google.com>, Leonard Kleinrock <lk@cs.ucla.edu>,
	 "David P. Reed" <dpreed@deepplum.com>,
	dickroy@alum.mit.edu, Dave Taht <dave.taht@gmail.com>,
	 Neal Cardwell <ncardwell@google.com>,
	Stuart Cheshire <cheshire@apple.com>,
	 Christoph Paasch <cpaasch@apple.com>,
	Matt Mathis <mattmathis@google.com>
Subject: [Make-wifi-fast] Network telemetry and non-parametric distributions
Date: Mon, 3 Jan 2022 16:23:52 -0800	[thread overview]
Message-ID: <CAHb6LvpRuPryDNRKU5OVB1NaOgcYf4NWcoWcCChBfpHc7Xv25A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]

Hi All,

Happy New Year! My apologies up front if this email is not of interest
and hence spam to you.

I was hoping to get some technical feedback from industry networking and
queuing experts with respect to latency fault detection and forwarding path
decisions. Iperf 2 <https://sourceforge.net/projects/iperf2/> flows code
produces dendrograms (ward clustering) with respect to e2e latencies.
(Latencies can be video frames, write to reads, packets, etc.) The metric
used to populate the distance matrices comes per the Kolmogorov Smirnov
<https://en.wikipedia.org/wiki/Kolmogorov%E2%80%93Smirnov_test> two sample
test which supports comparing non-parametric distributions.

WiFi 6 plans to use MU transmissions to reduce latency as one TXOP or
scheduled trigger can TX multiple AP/STA packets, i.e. kinda a form of
multicast (just doesn't use L2 MCAST DAs but rather does it in the RF
domain.)

I'm wondering about realtime detection of "latency timing violations," and
possibly using ML to identify better low latency path trees (LLPT)
analogous to IP multicast RPT and SPT. The idea is to cluster the graphs in
a way that packets get probabilistically bunched into microbursts per the
final AP's MU groups (since it's assumed the last hop is WiFi.)

Does this seem technically reasonable and, if so, is there a
reasonable return on the engineering? I'd like to prototype it with iperf
2, python (pyflows) and on some test rigs but it's a lot of work and I
don't want to take on that work if the return on engineering (ROE) is near
zero.

Thanks in advance for your thoughts and opinions,
Bob

-- 
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 #2: Type: text/html, Size: 2584 bytes --]

                 reply	other threads:[~2022-01-04  0:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAHb6LvpRuPryDNRKU5OVB1NaOgcYf4NWcoWcCChBfpHc7Xv25A@mail.gmail.com \
    --to=bob.mcmahon@broadcom.com \
    --cc=cheshire@apple.com \
    --cc=cpaasch@apple.com \
    --cc=dave.taht@gmail.com \
    --cc=dickroy@alum.mit.edu \
    --cc=dpreed@deepplum.com \
    --cc=lk@cs.ucla.edu \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=mattmathis@google.com \
    --cc=ncardwell@google.com \
    --cc=vint@google.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