From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: David Lang <david@lang.hm>, cake@lists.bufferbloat.net
Subject: Re: [Cake] A few puzzling Cake results
Date: Thu, 19 Apr 2018 12:32:35 +0300 [thread overview]
Message-ID: <130F35DD-8AC7-4AE8-B7AB-82AE5B2F7653@gmail.com> (raw)
In-Reply-To: <871sfb1rg5.fsf@toke.dk>
> If you turn off the AQM entirely for the
> first four packets, it is going to activate when the fifth packet
> arrives, resulting in a tail loss and... an RTO!
That isn't what happens.
First of all, Cake explicitly guards against tail loss by exempting the last packet in each queue from being dropped. If a tail loss and RTO actually occurs, it's extremely unlikely that Cake caused it, unless it's been driven far beyond its design load in terms of flow count.
Secondly, and as you should very well know, Codel only starts marking or dropping when the *standing* queue exceeds the threshold set. COBALT implements that logic in a different way to the reference version, but it's still there. It's not a case of the fifth packet in a flow getting dropped, but of a five-packet standing queue being the smallest that *can* experience drops.
So please don't strawman this.
- Jonathan Morton
prev parent reply other threads:[~2018-04-19 9:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 9:42 Toke Høiland-Jørgensen
2018-04-17 10:04 ` Luca Muscariello
2018-04-17 10:38 ` Toke Høiland-Jørgensen
2018-04-17 12:05 ` Y
[not found] ` <mailman.225.1523966725.3573.cake@lists.bufferbloat.net>
2018-04-17 12:22 ` Toke Høiland-Jørgensen
2018-04-17 13:16 ` Jonas Mårtensson
2018-04-17 13:50 ` Toke Høiland-Jørgensen
2018-04-17 13:47 ` Luca Muscariello
2018-04-17 13:52 ` Luca Muscariello
2018-04-17 14:25 ` Toke Høiland-Jørgensen
2018-04-17 14:54 ` Luca Muscariello
2018-04-17 15:10 ` Toke Høiland-Jørgensen
2018-04-17 14:03 ` Jonathan Morton
2018-04-17 14:17 ` Toke Høiland-Jørgensen
2018-04-18 11:25 ` Toke Høiland-Jørgensen
2018-04-18 12:21 ` Kevin Darbyshire-Bryant
2018-04-18 12:57 ` Toke Høiland-Jørgensen
2018-04-18 13:13 ` Jonas Mårtensson
2018-04-18 13:21 ` Toke Høiland-Jørgensen
2018-04-18 14:12 ` Jonathan Morton
2018-04-18 14:30 ` Toke Høiland-Jørgensen
2018-04-18 15:03 ` Jonathan Morton
2018-04-18 15:17 ` Sebastian Moeller
2018-04-18 15:58 ` Jonathan Morton
2018-04-18 16:11 ` Toke Høiland-Jørgensen
2018-04-18 16:25 ` Dave Taht
2018-04-18 16:34 ` Georgios Amanakis
2018-04-18 17:10 ` Sebastian Moeller
2018-04-19 7:49 ` Luca Muscariello
2018-04-19 8:11 ` Jonathan Morton
2018-04-19 9:00 ` Toke Høiland-Jørgensen
2018-04-19 9:21 ` Jonathan Morton
2018-04-19 9:26 ` Toke Høiland-Jørgensen
2018-04-19 9:55 ` Jonathan Morton
2018-04-19 10:33 ` Toke Høiland-Jørgensen
2018-04-19 11:55 ` Luca Muscariello
2018-04-18 16:54 ` Jonathan Morton
2018-04-18 17:02 ` Dave Taht
2018-04-18 18:06 ` Jonas Mårtensson
2018-04-18 18:11 ` Toke Høiland-Jørgensen
2018-04-18 18:16 ` Kevin Darbyshire-Bryant
[not found] ` <mailman.238.1524075384.3573.cake@lists.bufferbloat.net>
2018-04-19 8:31 ` Kevin Darbyshire-Bryant
2018-04-18 18:11 ` Jonas Mårtensson
2018-04-18 19:53 ` David Lang
2018-04-18 21:53 ` Jonathan Morton
2018-04-19 9:22 ` Toke Høiland-Jørgensen
2018-04-19 9:32 ` Jonathan Morton [this message]
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=130F35DD-8AC7-4AE8-B7AB-82AE5B2F7653@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=toke@toke.dk \
/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