Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Bob McMahon <bob.mcmahon@broadcom.com>
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 12:23:30 +0100	[thread overview]
Message-ID: <875y01xwi5.fsf@toke.dk> (raw)
In-Reply-To: <CAHb6LvrtfR89udToSxuYYpqyYRe3Dy+Vc5jNPJu7jrY93WUy+g@mail.gmail.com>

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

  reply	other threads:[~2024-01-10 11: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 [this message]
2024-01-10 13:55         ` XianJun Jiao
2024-01-10 15:47           ` Dave Taht
2024-01-10 18:23         ` Bob McMahon
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=875y01xwi5.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=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