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 0B0D33B29E;
 Tue, 22 Nov 2022 15:03:56 -0500 (EST)
Received: from asgard.lang.hm (syslog [10.0.0.100])
 by mail.lang.hm (Postfix) with ESMTP id B963315A80B;
 Tue, 22 Nov 2022 12:03:54 -0800 (PST)
Date: Tue, 22 Nov 2022 12:03:54 -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: <CAHb6LvrK_exkt_rbukYkF4_hwPXyy9T+ZNGzdK79x91RrK49Mg@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.2211221202210.4070@nftneq.ynat.uz>
References: <CAA93jw6yJU10wh9ajqX4yW2AvnJPStyWAAcV4+oQ8wSGsJgKZA@mail.gmail.com>
 <CAHb6LvrK_exkt_rbukYkF4_hwPXyy9T+ZNGzdK79x91RrK49Mg@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:03:56 -0000

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