Re: [Make-wifi-fast] [bbr-dev] Aggregating without bloating - hard times for tcp and wifi

[Bob McMahon <bob.mcmahon@broadcom.com>]

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

An AP's radio complex may have a CPU but that doesn't mean it is the
standard linux stack as most think of it. Many consider this as part of
"firmware" which can be Linux, a Linux derivative or other.  Also, there
are some levels of wired/wireless forwarding plane integration done at the
hardware level that many might be surprised by.

Bob

On Tue, Nov 22, 2022 at 12:03 PM David Lang <david@lang.hm> wrote:

> On Tue, 22 Nov 2022, Bob McMahon via Make-wifi-fast wrote:
>
> > Finally, many (most?) APs are forwarding and feeding packets at at the
> > hardware level so not sure that the linux stack matters as much for an AP
> > based analysis, particularly when considering multi user transmissions,
> > i.e. multiple WiFi clients are active and sharing TXOPs.
>
> APs forward packets within the switch at the hardware level, but the
> radios have
> to go through the CPU, so any wired <-> wireless needs to go through the
> CPU,
> and I would be incredibly surprised if the wifi chips did wireless <->
> wireless
> routing at the hardware level.
>
> David Lang
>

-- 
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: 2286 bytes --]

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