General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Tom Henderson <tomh@tomh.org>
To: Daniel Sterling <sterling.daniel@gmail.com>, davecb@spamcop.net
Cc: Jonathan Morton <chromatix99@gmail.com>,
	"dave.collier-brown@indexexchange.com"
	<dave.collier-brown@indexexchange.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Mon, 10 Aug 2020 08:08:49 -0700	[thread overview]
Message-ID: <d23ef628-8109-f0b2-526e-cd21f25ca5c8@tomh.org> (raw)
In-Reply-To: <CAJZMiudg4i1aH+H1F1GEBcxwUdFFYj8OsicPK2gwEFMzjiNGAQ@mail.gmail.com>


> so after much tweaking, I've got cake set to 40mbit down, 20mbit up,
> enforced by two cakes (one for each NIC). that's fairly low --

Thanks for sharing this configuration experience, but it leads me back 
to a question I have about best current practice for deployment.  Can 
CAKE/SQM handle dynamic Wi-Fi bandwidth due to Wi-Fi rate control 
selecting lower MCS to increase range, or does it rely on first getting 
the Wi-Fi deployed so that it has strong signal everywhere, and then 
finding a CAKE shaping rate that shaves off a few Mb/s from the highest 
capacity MCS so that the bottleneck always lands on the CAKE AQM?  It 
seems like the deployment that you shared with a separate router will 
require a predictable Wi-Fi rate, but I am wondering more about the case 
in which CAKE is deployed on the AP.

- Tom


  reply	other threads:[~2020-08-10 15:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 18:27 David Collier-Brown
2020-08-09 19:18 ` Tom Henderson
2020-08-09 21:35   ` Jonathan Morton
2020-08-10 12:57     ` David Collier-Brown
2020-08-10 14:00       ` Daniel Sterling
2020-08-10 15:08         ` Tom Henderson [this message]
2020-08-10 15:34           ` Sebastian Moeller
2020-08-10 15:57             ` Jonathan Morton
2020-08-10 16:04               ` Tom Henderson
2020-08-11 12:43         ` Daniel Sterling
2020-08-11 13:57           ` Kenneth Porter
     [not found]           ` <D8B6D86243E4539BBA58E32C@172.27.17.193>
2020-08-11 14:09             ` Daniel Sterling
2020-08-11 14:11               ` Daniel Sterling
2020-08-11 16:19                 ` Kenneth Porter
2020-08-10 17:58       ` Jonathan Foulkes
2020-08-10 19:13         ` Carlos R. Pasqualini
2020-08-10 20:28         ` Dave Collier-Brown
2020-08-11 12:41           ` Michael Yartys
2020-08-10 14:16     ` [Bloat] Sidebar to "How about a topical LWN article on demonstrating the real-world goodness of CAKE?" David Collier-Brown
2020-08-11 15:48     ` [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE? Simon Barber
2020-09-05 18:52 ` Dave Taht
2020-09-05 20:35   ` Dave Collier-Brown
2020-09-07  9:23     ` Toke Høiland-Jørgensen
2020-09-07 11:33       ` Dave Collier-Brown
2020-09-07 17:20         ` David Collier-Brown
2020-09-08 15:43           ` Dave Taht
2020-09-08 16:48             ` Matt Mathis
2020-09-08 17:09               ` Jonathan Morton
2020-09-10 15:08                 ` Anthony Minessale II
2020-09-10 16:52                   ` Dave Collier-Brown

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

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

  git send-email \
    --in-reply-to=d23ef628-8109-f0b2-526e-cd21f25ca5c8@tomh.org \
    --to=tomh@tomh.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.collier-brown@indexexchange.com \
    --cc=davecb@spamcop.net \
    --cc=sterling.daniel@gmail.com \
    /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