From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from mail.lang.hm (unknown [66.167.227.145])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 6A9493B29E;
 Tue, 22 Nov 2022 15:16:25 -0500 (EST)
Received: from asgard.lang.hm (syslog [10.0.0.100])
 by mail.lang.hm (Postfix) with ESMTP id 3E5B715A81C;
 Tue, 22 Nov 2022 12:16:24 -0800 (PST)
Date: Tue, 22 Nov 2022 12:16:24 -0800 (PST)
From: David Lang <david@lang.hm>
X-X-Sender: dlang@asgard.lang.hm
To: Bob McMahon <bob.mcmahon@broadcom.com>
cc: Dave Taht <dave.taht@gmail.com>, 
 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>, 
 BBR Development <bbr-dev@googlegroups.com>, 
 bloat <bloat@lists.bufferbloat.net>
In-Reply-To: <CAHb6LvqpVGLwN7ynT9BvsawOL_q3aY2vca7bEZKtsebN9KTtwA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.2211221214470.4070@nftneq.ynat.uz>
References: <CAA93jw6yJU10wh9ajqX4yW2AvnJPStyWAAcV4+oQ8wSGsJgKZA@mail.gmail.com>
 <CAHb6LvrK_exkt_rbukYkF4_hwPXyy9T+ZNGzdK79x91RrK49Mg@mail.gmail.com>
 <alpine.DEB.2.02.2211221202210.4070@nftneq.ynat.uz>
 <CAHb6LvqpVGLwN7ynT9BvsawOL_q3aY2vca7bEZKtsebN9KTtwA@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [Bloat] [Make-wifi-fast] [bbr-dev] Aggregating without bloating
 - hard times for tcp and wifi
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2022 20:16:25 -0000

sorry, when I was saying 'the cpu', I was meaning the main one running linux, 
not something that's part of the wifi chipset.

I would be very surprised if the wifi chipset is doing any packet routing, as 
opposed to just sending the packets to the main processor.

Remember, the common case isn't forwarding from one wifi device to another, it's 
moving between wifi devices and the wired uplink.

David Lang

On Tue, 22 Nov 2022, Bob McMahon wrote:

> 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
>>
>
>