From: Bob McMahon <bob.mcmahon@broadcom.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] a cheer up tweet for y'all
Date: Wed, 10 Jan 2024 10:23:11 -0800 [thread overview]
Message-ID: <CAHb6LvoyDXcdrjaNTQDK68HQUMwP7ATUO8COUDwwoMQVv6nnLg@mail.gmail.com> (raw)
In-Reply-To: <875y01xwi5.fsf@toke.dk>
[-- Attachment #1.1: Type: text/plain, Size: 3037 bytes --]
> Well, the original context of the question was "Linux WiFi drivers are
> terrible, what can we do about that", and, well, providing proper
> upstream drivers at HW launch is the way to solve that.
This is out of the scope of chip makers for modern chips. The os drivers
are written by system integrators - specialization has divided these tasks.
Chip makers don't affect open vs closed source drivers of systems. Think
of a WiFi chip now as transistors with a small microcontroller and not a
linux NIC.
One can argue that chip makers don't provide documents to open-source
developers, which is mostly accurate. But documents aren't the blocker.
I think an open source community would have to innovate to a level to drive
the use of chips coming off a foundry line for a chip maker to consider
assigning resources to support open-source teams. Old chips with 10+ year
old NRE doesn't justify any investment by anyone.
I think the server market & structure & level of cloud innovation make
things different for ethernet NICs.
Bob
On Wed, Jan 10, 2024 at 3:23 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Bob McMahon <bob.mcmahon@broadcom.com> writes:
>
> > This approach is not going to work. Sun workstations as the forwarding
> > planes for WiFi doesn't work nor scale and is cost & power inefficient.
> The
> > WiFi forwarding plane needs to be all hardware and not based off of BSD.
> It
> > has to be like a port asic in an ethernet switch. No SoC.
> >
> > Ethernet NICs are targeting servers where the workstation/NIC model does
> > work. WiFi is never going to be the basis for cloud servers.
>
> Well, the original context of the question was "Linux WiFi drivers are
> terrible, what can we do about that", and, well, providing proper
> upstream drivers at HW launch is the way to solve that.
>
> And even so, every Linux-based CPE in existence is a contradiction of
> you assertion that software-based WiFi forwarding is "not going to
> work". On the contrary, the SOCs with proper open source drivers and
> support are the ones that work the best, because that means we can run
> OpenWrt on them instead of the vendor crapware that they ship with.
>
> -Toke
>
--
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: 3583 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2024-01-10 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 17:19 Dave Taht
2024-01-09 4:41 ` Bob McMahon
2024-01-09 10:56 ` Toke Høiland-Jørgensen
2024-01-09 11:36 ` Dave Taht
2024-01-09 17:42 ` Bob McMahon
2024-01-10 11:23 ` Toke Høiland-Jørgensen
2024-01-10 13:55 ` XianJun Jiao
2024-01-10 15:47 ` Dave Taht
2024-01-10 18:23 ` Bob McMahon [this message]
2024-01-11 9:31 ` Dave Taht
2024-01-11 17:29 ` 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=CAHb6LvoyDXcdrjaNTQDK68HQUMwP7ATUO8COUDwwoMQVv6nnLg@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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