From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: 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: Fri, 24 Jan 2020 12:49:36 -0800 [thread overview]
Message-ID: <CAHb6Lvpv7VKsRSffR_hvLAPd0PZ66mFJrBC8BMOOXpv4eR9uNg@mail.gmail.com> (raw)
In-Reply-To: <69103D46-8F04-4468-802B-142CC2DABF0F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
I haven't thought this out but 802.11ax is very different per things like
AP based scheduling of transmits (trigger frames), assigning to RU (sub
carriers), and per STA tx power control. I think the implementations of
these is outside the standard as well. Those writing traffic schedulers
will mostly likely be impacted.
Bob
On Fri, Jan 24, 2020 at 6: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.
>
>
> _______________________________________________
> 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: 1490 bytes --]
next prev parent reply other threads:[~2020-01-24 20:49 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 [this message]
[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
[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=CAHb6Lvpv7VKsRSffR_hvLAPd0PZ66mFJrBC8BMOOXpv4eR9uNg@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--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