Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: dave seddon <dave.seddon.ca@gmail.com>,
	dave seddon via Cake <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Mon, 16 Oct 2023 06:52:04 +0300	[thread overview]
Message-ID: <444AAB44-8AE2-4812-BAE7-672A0B5489DC@gmail.com> (raw)
In-Reply-To: <1697401792.32573388@apps.rackspace.com>

> On 15 Oct, 2023, at 11:29 pm, David P. Reed via Cake <cake@lists.bufferbloat.net> wrote:
> 
> Of course, Internet congestion control, in general, is still stuck in the original Van Jacobsen sawtooth era. My guess is it won't get fixed, though I applaud Cake, and despair the hardware folks who keep adding buffers.

I am still working in this area, including on a revised version of SCE which might regain traction in the IETF.

One of the more immediate results of this is a new AQM algorithm which builds on the success of Codel, and a family of qdiscs I'm building around it.  These range from a queueless traffic policer to a "Cake version 2", with an interesting approximate-fairness approach for the middle child.  The AQM itself is already working, though not yet documented in a public-facing form.

I'm also taking a new approach to overlaying the "small" congestion response of SCE over the "big" response of conventional congestion control, which I think is capable of solving several long-standing problems in one go.  I'll say more when we have a working prototype - but think in terms of "no sawtooth" and "naturally max-min fair".  TCP Prague will look positively primitive compared to this - if it works (and it should).

 - Jonathan Morton

  reply	other threads:[~2023-10-16  3:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  1:05 Dave Taht
2023-09-18  1:25 ` Jonathan Morton
2023-09-18 16:57 ` David P. Reed
2023-09-18 19:50 ` dave seddon
2023-09-18 20:24   ` David P. Reed
2023-09-18 22:07     ` Jonathan Morton
2023-09-28 11:44       ` Jonathan Morton
2023-09-28 12:15         ` Sebastian Moeller
2023-09-28 12:33           ` Jonathan Morton
2023-09-28 12:56             ` David Lang
2023-09-28 13:08             ` Sebastian Moeller
2023-09-28 13:19               ` David Lang
2023-09-28 13:27                 ` Sebastian Moeller
2023-10-13 15:59                   ` dave seddon
2023-10-13 17:25                     ` dave seddon
2023-10-15 15:11                       ` dave seddon
2023-10-15 15:52                         ` Sebastian Moeller
2023-10-15 16:24                           ` dave seddon
2023-10-15 20:29                             ` David P. Reed
2023-10-16  3:52                               ` Jonathan Morton [this message]
2023-10-15 15:53                         ` Dave Taht
2023-10-23 20:31                         ` dave seddon
2023-10-23 20:35                           ` dave seddon
2023-10-24 16:27                           ` dave seddon
2023-10-24 21:35                             ` dave seddon
2023-10-24 22:06                               ` Dave Taht
2023-09-18 22:13   ` Jonathan Morton
2023-09-18 22:52     ` dave seddon
2023-09-18 23:08       ` Jonathan Morton

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=444AAB44-8AE2-4812-BAE7-672A0B5489DC@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.seddon.ca@gmail.com \
    --cc=dpreed@deepplum.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