Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel@quora.org>
To: cake@lists.bufferbloat.net
Subject: [Cake] WiFI/shared media and bursting
Date: Thu, 6 Oct 2022 16:06:37 +0800	[thread overview]
Message-ID: <CAMVG2suqK3DOrmE6vn6RpbdddOjVQxV-UF-8dxHRdsh_-5E=-w@mail.gmail.com> (raw)

Hi Dave, Toke et al,

Given various challenges brought by WiFi (and related radio frequency systems):
1. the maximum throughput varies by media attenuation (eg range) and
device capability, all else aside (ie isolated environment)
2. the upstream and downstream paths share the same media
3. the media is shared with other devices (increasing the noise floor)
and networks cause 802.11 Clear Channel Assessment to defer
transmission

For these reasons any bandwidth estimation (autorate) may be valid
only for 10s of milliseconds.

Therefore for a given density of access point deployment, there should
be a conservative throughput lower bound covering, for example 40Mbps
(peak unidir would be 120Mbps). Since this is shared among upload and
download, one could deploy CAKE with a fixed 20Mbps limit for upload
and 20Mbps for download.

A second approach might be to have a TBF or related scheme to allow
per-stream bursts, limiting them to 15Mbps (or less) steady-state
after a burst period. Though this defeats one aspect of CAKE, I'm
using this approach to attempt to manage latency better. It's worth
noting the Linux drivers I'm using aren't ath10k or such, so do
over-buffer.

Does anyone have any advice or experience on this or another scheme
with WiFi or related?

Thanks,
  Dan
--
Daniel J Blueman

                 reply	other threads:[~2022-10-06  8:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMVG2suqK3DOrmE6vn6RpbdddOjVQxV-UF-8dxHRdsh_-5E=-w@mail.gmail.com' \
    --to=daniel@quora.org \
    --cc=cake@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