Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave@taht.net>
Cc: Rich Brown <richb.hanover@gmail.com>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Wi-Fi 6 - how many of our assumptions does it violate?
Date: Thu, 30 Jan 2020 17:20:09 -0800	[thread overview]
Message-ID: <CAHb6Lvr+ZwbaR3s+R14=_H4KjR3puUkw1DXLYwdpz36eGsB+gg@mail.gmail.com> (raw)
In-Reply-To: <87a764ziiy.fsf@taht.net>

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

It's part of the reasons iperf 2.0.14 has so many new latency, trip-time,
start-time, connect, etc related features. Peak avg throughput is no longer
a valid proxy for "performance."

From a testing view, attenuation or range is no longer sufficient either.
Phase shifters are needed per things like VR/AR as truly optimizing the
number of spatial streams is needed too.

The loss function(s) to be optimized (minimized) is far from trivial in
both the definition and in [re]-computing in "real-time"

WiFi engineers have more work to do.

Bob

On Thu, Jan 30, 2020 at 2:28 PM Dave Taht <dave@taht.net> wrote:

> Rich Brown <richb.hanover@gmail.com> writes:
>
> >> On Jan 24, 2020, at 9:06 AM, Rich Brown <richb.hanover@gmail.com>
> wrote:
> >>
> >> I saw this overview of the now-in-testing Wi-Fi 6 at
> >>
> https://www.howtogeek.com/368332/wi-fi-6-what%E2%80%99s-different-and-why-it-matters/
> >>
> >> Its multiple MIMO streams and maybe talking to multiple devices at a
> >> time seem as if they might be outside the assumptions we use.
> >
> > It's worse than I thought. I just watched this explainer video from
> > ExtremeNetworks: https://www.youtube.com/watch?v=owBrkFk9afM
> >
> > If I understand correctly, they want the AP to solve a hard
> > (bin-packing) problem, in real-time, with unclear rules for maximizing
> > client goals (should the VoIP packet go first?). And no mention of
> > airtime fairness or latency...
> >
> > Or am I missing something? Thanks.
>
> No, they punted on these things in the design.
>
> >
> > Rich
> > _______________________________________________
> > Make-wifi-fast mailing list
> > Make-wifi-fast@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/make-wifi-fast
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

[-- Attachment #2: Type: text/html, Size: 3117 bytes --]

  reply	other threads:[~2020-01-31  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 14:06 Rich Brown
2020-01-24 20:49 ` Bob McMahon
     [not found] ` <mailman.389.1579898991.1241.make-wifi-fast@lists.bufferbloat.net>
2020-01-25 15:41   ` Dave Taht
2020-01-27 14:20 ` Rich Brown
2020-01-30 22:28   ` Dave Taht
2020-01-31  1:20     ` Bob McMahon [this message]
     [not found]     ` <mailman.414.1580433623.1241.make-wifi-fast@lists.bufferbloat.net>
2020-01-31  1:28       ` Dave Taht
2020-02-03 18:45         ` Bob McMahon

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='CAHb6Lvr+ZwbaR3s+R14=_H4KjR3puUkw1DXLYwdpz36eGsB+gg@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=dave@taht.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=richb.hanover@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