From: Rich Brown <richb.hanover@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] sophgo risc-v wifi6 chip
Date: Mon, 29 Jul 2024 08:03:50 -0400 [thread overview]
Message-ID: <25576C4C-91D3-4050-82C8-49D1A6C417D8@gmail.com> (raw)
In-Reply-To: <mailman.1.1722182401.12366.make-wifi-fast@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
> On Jul 28, 2024, at 12:00 PM, make-wifi-fast-request@lists.bufferbloat.net wrote:
>
> Here, the solutions need to be in full transistors
> (and very low power and very secure.) ... Wi-Fi doesn't need to be
> managed by a complex workstation and 30+ years of software bloat.
If I understand the argument, it's that we should have a pared-down Wi-Fi chip that does exactly one thing, and does it well. It should implement all the best practices (TXQs, ATF, AQL, etc.) to make it (more) secure, deliver the best performance (speed & latency).
The fact that the algorithms are permanently welded into the silicon doesn't really matter: in practice, "no one ever updates their Wi-Fi drivers" in the bazillions of off-the-shelf routers on the market. They might as well have a good implementation.
Do I have that right? Thanks.
Rich
[-- Attachment #2: Type: text/html, Size: 3652 bytes --]
next parent reply other threads:[~2024-07-29 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1722182401.12366.make-wifi-fast@lists.bufferbloat.net>
2024-07-29 12:03 ` Rich Brown [this message]
2024-07-29 17:01 ` Bob McMahon
2024-07-26 22:57 Dave Taht
2024-07-27 21:23 ` 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=25576C4C-91D3-4050-82C8-49D1A6C417D8@gmail.com \
--to=richb.hanover@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