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 B687A3B29E;
 Thu,  2 Dec 2021 04:09:50 -0500 (EST)
Received: from dlang-mobile (unknown [10.2.2.69])
 by mail.lang.hm (Postfix) with ESMTP id 9583D1148C1;
 Thu,  2 Dec 2021 01:09:49 -0800 (PST)
Date: Thu, 2 Dec 2021 01:09:49 -0800 (PST)
From: David Lang <david@lang.hm>
To: =?ISO-8859-15?Q?Toke_H=F8iland-J=F8rgensen?= <toke@toke.dk>
cc: =?UTF-8?Q?Valdis_Kl=C4=93tnieks?= <valdis.kletnieks@vt.edu>, 
 David Lang <david@lang.hm>, 
 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>, 
 "David P. Reed" <dpreed@deepplum.com>, bloat <bloat@lists.bufferbloat.net>
In-Reply-To: <87mtlj6f4g.fsf@toke.dk>
Message-ID: <34643258-8or9-sppr-179-307553o21p20@ynat.uz>
References: <CAA93jw48R8YfCR6TPWwdsDPA1=gzJjRMKo6c0nxfWvKt1ws0tQ@mail.gmail.com>
 <1638390391.091227727@apps.rackspace.com>
 <alpine.DEB.2.02.2112011307210.6080@nftneq.ynat.uz>
 <119212.1638397736@turing-police> <87mtlj6f4g.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="228850167-1056173681-1638436189=:5726"
Subject: Re: [Bloat] [Cerowrt-devel] uplink bufferbloat and scheduling
 problems
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: Thu, 02 Dec 2021 09:09:50 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--228850167-1056173681-1638436189=:5726
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 2 Dec 2021, Toke Høiland-Jørgensen wrote:

> "Valdis Klētnieks" <valdis.kletnieks@vt.edu> writes:
>
>> On Wed, 01 Dec 2021 13:09:46 -0800, David Lang said:
>>
>>> with wifi where you can transmit multiple packets in one airtime slot, you need
>>> enough buffer to handle the entire burst.
>>
>> OK, I'll bite... roughly how many min-sized or max-sized packets can you fit
>> into one slot?
>
> On 802.11n, 64kB; on 802.11ac, 4MB(!); on 802.11ax, no idea - the same as 802.11ac?

As I understnad it, 802.11ax can do 16MB (4MB to each of 4 different endpoints)

This is made significantly messier because the headers for each transmission are 
sent at FAR slower rates than the data can be, so if you send a single 64 byte 
packet in a timeslot that could send 4/16MB, it's not a matter of taking 
1/128,000 of the time (the ratio of the data), it's more like 1/2 of the 
time.

So it's really valuable for overall throughput to fill those transmit slots 
rather than having the data trickle out over many slots.

David Lang
--228850167-1056173681-1638436189=:5726--