From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>, cake@lists.bufferbloat.net
Subject: Re: [Cake] A few puzzling Cake results
Date: Wed, 18 Apr 2018 17:17:11 +0200 [thread overview]
Message-ID: <0BB8B1FD-6A00-49D6-806E-794BD53A449F@gmx.de> (raw)
In-Reply-To: <FCA9E4F3-EA5C-4223-BA23-771C993867AF@gmail.com>
> On Apr 18, 2018, at 17:03, Jonathan Morton <chromatix99@gmail.com> wrote:
> [...]
>>> Without that, we can end up with very high drop rates which, in
>>> ingress mode, don't actually improve congestion on the bottleneck link
>>> because TCP can't reduce its window below 4 MTUs, and it's having to
>>> retransmit all the lost packets as well. That loses us a lot of
>>> goodput for no good reason.
>>
>> I can sorta, maybe, see the point of not dropping packets that won't
>> cause the flow to decrease its rate *in ingress mode*. But this is also
>> enabled in egress mode, where it doesn't make sense.
>
> I couldn't think of a good reason to switch it off in egress mode. That would improve a metric that few people care about or can even measure, while severely increasing packet loss and retransmissions in some situations, which is something that people *do* care about and measure.
[...]
Just a thought, in egress mode in the typical deployment we expect, the bandwidth leading into cake will be >> than the bandwidth out of cake, so I would argue that the package droppage might be acceptable on egress as there is bandwidth to "waste" while on ingress the issue very much is that all packets cake sees already used up parts of the limited transfer time on the bottleneck link and hence are more "precious", no? Users wanting this new behavior could still use the ingress keyword even on egress interfaces?
Best Regards
Sebastian
next prev parent reply other threads:[~2018-04-18 15:17 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 [this message]
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
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=0BB8B1FD-6A00-49D6-806E-794BD53A449F@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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