Lets make wifi fast again!
 help / color / mirror / Atom feed
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: Tue, 9 Jan 2024 09:42:17 -0800	[thread overview]
Message-ID: <CAHb6LvrtfR89udToSxuYYpqyYRe3Dy+Vc5jNPJu7jrY93WUy+g@mail.gmail.com> (raw)
In-Reply-To: <877cki4vxq.fsf@toke.dk>


[-- Attachment #1.1: Type: text/plain, Size: 1908 bytes --]

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.

Bob

On Tue, Jan 9, 2024 at 2:56 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Bob McMahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net>
> writes:
>
> > What are you expecting from chip makers?
>
> High-quality open source drivers, upstreamed into the Linux mainline by
> the time the hardware ships, would be a good start :)
>
> Vendors seem to manage this for Ethernet NICs just fine, so it can't
> really be a technical barrier that is keeping this from happening.
>
> If we're going further down the wish list, "no binary firmware blobs"
> would be next as far as I'm concerned. Not holding my breath on that
> one, though :/
>
> -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: 2386 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  parent reply	other threads:[~2024-01-09 17:42 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 [this message]
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
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=CAHb6LvrtfR89udToSxuYYpqyYRe3Dy+Vc5jNPJu7jrY93WUy+g@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