From: Jonathan Morton <chromatix99@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] diffserv3 vs diffserv4
Date: Sun, 26 Jul 2020 00:27:54 +0300 [thread overview]
Message-ID: <56BAD843-DB8B-41AF-BC1A-D29BAAD23680@gmail.com> (raw)
In-Reply-To: <1595705720.093911757@apps.rackspace.com>
> On 25 Jul, 2020, at 10:35 pm, David P. Reed <dpreed@deepplum.com> wrote:
>
> And to be clear, AQM (cake, being an example) is not about bandwidth allocation. It does focus on latency/queueing-delay, for the most part.
Cake is not *just* an AQM, though I understand your point. It is a qdisc with many interwoven functions.
Cake's Diffserv support is neither a pure priority scheme nor a pure bandwidth allocation. By using a hybrid of the two for bandwidth allocation, I was hoping to avoid the main pitfalls that the simple Bell-headed approaches routinely encounter. Each tin also has its own AQM parameters, which feed into the distinction between high-throughput and low-latency classes of traffic.
There are doubtless other approaches that could be tried, of course. And there might be endless debate over exactly how many traffic classes are actually needed; I don't think five is the right number, and the symmetry argument is not persuasive. But can we at least agree that Cake's attempt is a step in the right direction?
- Jonathan Morton
next prev parent reply other threads:[~2020-07-25 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 15:56 Justin Kilpatrick
2020-07-24 17:42 ` Kevin Darbyshire-Bryant
2020-07-25 10:12 ` Kevin Darbyshire-Bryant
2020-07-25 17:18 ` Sebastian Moeller
2020-07-25 17:47 ` Jonathan Morton
2020-07-25 17:48 ` David P. Reed
2020-07-25 17:54 ` Kevin Darbyshire-Bryant
2020-07-25 19:35 ` David P. Reed
2020-07-25 20:04 ` Sebastian Moeller
2020-07-25 21:33 ` Kevin Darbyshire-Bryant
2020-07-25 21:27 ` Jonathan Morton [this message]
2020-07-25 3:13 ` Jonathan Morton
2020-07-25 17:05 ` David P. Reed
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=56BAD843-DB8B-41AF-BC1A-D29BAAD23680@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=kevin@darbyshire-bryant.me.uk \
/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