From: "David P. Reed" <dpreed@deepplum.com>
To: "David Lang" <david@lang.hm>
Cc: "Bob McMahon" <bob.mcmahon@broadcom.com>,
"Cake List" <cake@lists.bufferbloat.net>,
"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>,
"Bob McMahon via Rpm" <rpm@lists.bufferbloat.net>,
"bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cake] [Rpm] [Bloat] The most wonderful video ever about bufferbloat
Date: Wed, 19 Oct 2022 17:26:31 -0400 (EDT) [thread overview]
Message-ID: <1666214791.81584918@apps.rackspace.com> (raw)
In-Reply-To: <qss576pn-2r55-84s9-s5ro-750570702685@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 3182 bytes --]
4 microseconds!
On Wednesday, October 19, 2022 3:23pm, "David Lang via Cake" <cake@lists.bufferbloat.net> said:
> you have to listen and hear nothing for some timeframe before you transmit, that
> listening time is define in the standard. (isn't it??)
>
> David Lang
>
> On Wed, 19 Oct 2022, Bob McMahon wrote:
>
> > I'm not sure where the gap in milliseconds is coming from. EDCA gaps are
> > mostly driven by probabilities
> > <https://link.springer.com/article/10.1007/s10270-020-00817-2>. If
> > energy detect (ED) indicates the medium is available then the gap prior to
> > transmit, assuming no others competing & winning at that moment in time, is
> > driven by AIFS and the CWMIN - CWMAX back offs which are simple probability
> > distributions. Things change a bit with 802.11ax and trigger frames but the
> > gap is still determined by the backoff and should be less than milliseconds
> > per that. Things like NAVs will impact the gap too but that happens when
> > another is transmitting.
> >
> >
> > [image: image.png]
> >
> > Agreed that the PLCP preamble is at low MCS and the payload can be orders
> > of magnitude greater (per different QAM encodings and other signal
> > processing techniques.)
> >
> > Bob
> >
> > On Wed, Oct 19, 2022 at 12:09 AM David Lang <david@lang.hm> wrote:
> >
> >> On Tue, 18 Oct 2022, Sebastian Moeller wrote:
> >>> Hi Bob,
> >>>
> >>>> Many network engineers typically, though incorrectly, perceive a
> >> transmit
> >>>> unit as one ethernet packet. With WiFi it's one Mu transmission
> or one
> >> Su
> >>>> transmission, with aggregation(s), which is a lot more than one
> ethernet
> >>>> packet but it depends on things like MCS, spatial stream powers,
> Mu
> >> peers,
> >>>> etc. and is variable. Some data center designs have optimized the
> >>>> forwarding plane for flow completion times so their equivalent
> transmit
> >>>> unit is a mouse flow.
> >>>
> >>> [SM] Is this driven more by the need to aggregate packets to amortize
> >> some cost over a larger payload or to reduce the scheduling overhead or
> to
> >> regularize things (as in fixed size DTUs used in DSL with G.INP
> >> retransmissions)?
> >>
> >> it's to amortize costs over a larger payload.
> >>
> >> the gap between transmissions is in ms, and the transmission header is
> >> transmitted at a slow data rate (both for backwards compatibility with
> >> older
> >> equipment that doesn't know about the higher data rate modulations)
> >>
> >> For a long time, the transmission header was transmitted at 1Mb (which is
> >> still
> >> the default in most equipment), but there is now an option to no longer
> >> support
> >> 802.11b equipment, which raises the header transmission time to 11Mb.
> >>
> >> These factors are so imbalanced compared to the top data rates available
> >> that
> >> you need to transmit several MB of data to have actual data use 50% of
> the
> >> airtime.
> >>
> >> David Lang
> >>
> >
> >
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
[-- Attachment #2: Type: text/html, Size: 4604 bytes --]
next prev parent reply other threads:[~2022-10-19 21:26 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:14 [Make-wifi-fast] " Dave Taht
2022-10-09 13:23 ` [Make-wifi-fast] [Bloat] " Nathan Owens
2022-10-10 5:52 ` Taraldsen Erik
2022-10-10 9:09 ` [Make-wifi-fast] [Cake] " Sebastian Moeller
2022-10-10 9:33 ` Taraldsen Erik
2022-10-10 9:40 ` Sebastian Moeller
2022-10-10 11:46 ` [Make-wifi-fast] [Bloat] [Cake] " Taraldsen Erik
2022-10-10 20:23 ` Sebastian Moeller
2022-10-11 6:08 ` [Make-wifi-fast] [Cake] [Bloat] " Taraldsen Erik
2022-10-11 6:35 ` Sebastian Moeller
2022-10-11 6:38 ` [Make-wifi-fast] [Bloat] [Cake] " Dave Taht
2022-10-11 11:34 ` Taraldsen Erik
2022-10-10 16:45 ` [Make-wifi-fast] [Cake] [Bloat] " Bob McMahon
2022-10-10 22:57 ` [Make-wifi-fast] [Bloat] [Cake] " David Lang
2022-10-11 0:05 ` Bob McMahon
2022-10-11 7:15 ` Sebastian Moeller
2022-10-11 16:58 ` Bob McMahon
2022-10-11 17:00 ` [Make-wifi-fast] [Rpm] " Dave Taht
2022-10-11 17:26 ` [Make-wifi-fast] " Sebastian Moeller
2022-10-11 17:47 ` Bob McMahon
2022-10-11 13:57 ` [Make-wifi-fast] [Rpm] " Rich Brown
2022-10-11 14:43 ` Dave Taht
2022-10-11 17:05 ` Bob McMahon
2022-10-11 18:44 ` Rich Brown
2022-10-11 22:24 ` Dave Taht
2022-10-12 17:39 ` Bob McMahon
2022-10-12 21:44 ` [Make-wifi-fast] [Cake] [Rpm] [Bloat] " David P. Reed
2022-10-13 17:45 ` [Make-wifi-fast] [Bloat] [Rpm] [Cake] " Livingood, Jason
2022-10-13 17:49 ` [Make-wifi-fast] [Rpm] [Bloat] " Dave Taht
2022-10-11 6:28 ` [Make-wifi-fast] [Cake] [Bloat] " Sebastian Moeller
2022-10-18 0:02 ` [Make-wifi-fast] " Stuart Cheshire
2022-10-18 2:44 ` Dave Taht
2022-10-18 2:51 ` [Make-wifi-fast] [Bloat] " Sina Khanifar
2022-10-18 3:15 ` [Make-wifi-fast] A quick report from the WISPA conference Dave Taht
2022-10-18 17:17 ` Sina Khanifar
2022-10-18 19:04 ` [Make-wifi-fast] [Bloat] " Sebastian Moeller
2022-10-20 5:15 ` Sina Khanifar
2022-10-20 9:01 ` Sebastian Moeller
2022-10-20 14:50 ` Jeremy Harris
2022-10-20 15:56 ` Sebastian Moeller
2022-10-20 17:59 ` Bob McMahon
2022-10-18 19:17 ` Sebastian Moeller
2022-10-18 2:58 ` [Make-wifi-fast] [Bloat] The most wonderful video ever about bufferbloat David Lang
2022-10-18 17:03 ` Bob McMahon
2022-10-18 18:19 ` [Make-wifi-fast] [Rpm] " Sebastian Moeller
2022-10-18 19:30 ` Bob McMahon
2022-10-19 7:09 ` David Lang
2022-10-19 19:18 ` Bob McMahon
2022-10-19 19:23 ` David Lang
2022-10-19 21:26 ` David P. Reed [this message]
2022-10-19 21:37 ` [Make-wifi-fast] [Cake] " David Lang
2022-10-19 20:44 ` [Make-wifi-fast] " Stuart Cheshire
2022-10-19 21:33 ` [Make-wifi-fast] [Bloat] " David Lang
2022-10-19 23:36 ` Stephen Hemminger
2022-10-20 14:26 ` [Make-wifi-fast] [Rpm] [Bloat] Traffic analogies (was: Wonderful video) Rich Brown
2022-10-19 21:46 ` [Make-wifi-fast] [Bloat] The most wonderful video ever about bufferbloat Michael Richardson
2022-12-06 19:17 ` Bob McMahon
2022-10-20 9:36 ` [Make-wifi-fast] [Rpm] " Sebastian Moeller
2022-10-20 18:32 ` Stuart Cheshire
2022-10-20 19:04 ` Bob McMahon
2022-10-20 19:12 ` Dave Taht
2022-10-20 19:31 ` Bob McMahon
2022-10-20 19:40 ` Sebastian Moeller
2022-10-21 17:48 ` Bob McMahon
2022-10-20 19:33 ` Sebastian Moeller
2022-10-20 19:33 ` Dave Taht
2022-10-26 20:38 ` Sebastian Moeller
2022-10-26 20:42 ` Dave Taht
2022-10-26 20:53 ` Sebastian Moeller
2022-10-18 18:07 ` [Make-wifi-fast] [Bloat] " Sebastian Moeller
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=1666214791.81584918@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.mcmahon@broadcom.com \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
/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