From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] I used to dream of a single wifi cpu, memory, and I/O
Date: Sun, 9 Jul 2023 22:40:17 -0700 [thread overview]
Message-ID: <CAHb6LvrJwVyG+ouwsg92Dd0VbAw6dV8CFSUJ7=bufuCWiDfCsA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5wO4B+MehJiZgcqBx7nh0v=RK--Zm0+y8gVMnOF9nLNw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2154 bytes --]
I wonder if treating WiFi like a transceiver is the better approach,
separating "the computer abstraction" from the remote radio head.
Then it's a RF Front End(s) / CMOS Radios / PHY(s) / 802.11 MAC(s) (lower)
/ 802.3 PAM4 / 100G SERDES / 4 1x25G VCSELs. Pluggable like an SFP.
The virtualized APs could support at least 10 and maybe 100s of these via
merchant switching silicon and could be kilometers away. The MACs lower
could be simplified to dual queue a la L4S. No need for 4 AC queues per
MAC. Might be able to throw away 802.11 retries too and let the upper
layers handle it.
May be a good time to simplify.
Bob
On Fri, Jul 7, 2023 at 2:25 PM Dave Taht via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
> preferably using some sort of async circuitry for minimum interference
> and power consumption. I figured, oh, 256MB would be more than enough
> for a 10Gbit router.
>
> Instead, we can now layer 64GB on die.
>
> https://blocksandfiles.com/2023/07/05/3d-stacked-dram-and-processor-cube/
>
> --
> Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos
> _______________________________________________
> 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: 2985 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2023-07-10 5:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 21:25 Dave Taht
2023-07-10 5:40 ` Bob McMahon [this message]
2023-07-10 19:02 ` Aaron Wood
2023-07-10 20:47 ` Bob McMahon
2023-07-10 21:29 ` David Lang
2023-07-10 22:49 ` Bob McMahon
2023-07-10 23:34 ` David Lang
2023-07-11 2:13 ` Bob McMahon
2023-07-11 3:02 ` David Lang
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='CAHb6LvrJwVyG+ouwsg92Dd0VbAw6dV8CFSUJ7=bufuCWiDfCsA@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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