From: Daniel Sterling <sterling.daniel@gmail.com>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Tue, 11 Aug 2020 10:09:35 -0400 [thread overview]
Message-ID: <CAJZMiufEgVaFbrwjO4K7tU=jwtawpynAwvbypQwCtWXuNHCumg@mail.gmail.com> (raw)
In-Reply-To: <D8B6D86243E4539BBA58E32C@172.27.17.193>
as far as I know it's much simpler; I literally just turn on cake per
NIC with the correct settings applied for my environment
the env settings that matter are: which NIC is WAN vs LAN; and how
much bandwidth you want cake to enforce.
Also I find I get best results with "besteffort" vs using any of
cake's internal additional queues. I don't have enough visibility into
how cake is working to know what exactly is happening, and it may be
I'm confounding cake with some other env issue, but I've stuck with
besteffort due to seeing more latency when I turn on multiple cake
queues
On Tue, Aug 11, 2020 at 9:57 AM Kenneth Porter <shiva@sewingwitch.com> wrote:
>
> --On Tuesday, August 11, 2020 9:43 AM -0400 Daniel Sterling
> <sterling.daniel@gmail.com> wrote:
>
> > as promised here is the script I run after rebooting my openwrt box,
> > to set up cake
> >
> > https://gist.github.com/eqhmcow/c378c46a41aa5716767a0da811087dd4
>
> How does this differ from the sqm-scripts available in Fedora and OpenWrt?
>
> https://github.com/tohojo/sqm-scripts
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-08-11 14:09 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
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 [this message]
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='CAJZMiufEgVaFbrwjO4K7tU=jwtawpynAwvbypQwCtWXuNHCumg@mail.gmail.com' \
--to=sterling.daniel@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=shiva@sewingwitch.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