From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake for net-next 4.8
Date: Tue, 27 Sep 2016 21:56:53 +0300 [thread overview]
Message-ID: <27B5A7E3-203D-468F-B487-BFFC9294D857@gmail.com> (raw)
In-Reply-To: <CAA93jw6cT7hpVXhtn7R__d4KO-X1b2jsPSkyWp4YKGOEdUNycg@mail.gmail.com>
> On 27 Sep, 2016, at 21:18, Dave Taht <dave.taht@gmail.com> wrote:
>
>> On Tue, Sep 27, 2016 at 10:52 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>> On 25 Sep, 2016, at 21:30, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> Judging from me tearing apart how TCP BBR works (presently) with ecn,
>>> it looks like we need to add the equivalent to fq_codel ce_threshold
>>> behaviors as well.
>>
>> If I’m reading the legend correctly, you are setting ce_threshold to 1ms to get the better-controlled result. But that effectively disables the codel algorithm and turns it into a simple “mark all packets over 1ms sojourn” for ECN capable traffic, because it’s a tighter limit than codel’s target. That’s too aggressive for non-BBR traffic.
>
> Yes it is. :) However the consensus appears to be that ECN should be
> an earlier signal than drop, and the work over on the tcp-prague list
> centers around repurposing ECT(1) as more like a DCTCP multi-bit
> signal.
My interpretation of the consensus is more subtle: we need a signal earlier than we currently do, and with a weaker meaning, but we still need the strong, later signal.
I don’t think we should use CE for that; it has a long-established and widely-deployed meaning. We *can* use ECT(1), which is presently unused in practice.
> I'm really not sure if what I've seen with ce_threshold is the
> desired behavior, vs a vs BBR, thus far - but I'd like to see the
> option for it enter cake.
Before I even consider doing that, could you add a comparable run with the current version of cake to that graph? COBALT is not quite identical to Codel, and this looks like a case where one of the differences could be important.
- Jonathan Morton
next prev parent reply other threads:[~2016-09-27 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 18:30 Dave Taht
2016-09-27 14:38 ` Jonathan Morton
2016-09-27 16:04 ` Dave Taht
2016-09-27 16:13 ` Jonathan Morton
2016-09-29 23:22 ` Neil Shepperd
2016-09-30 8:02 ` Toke Høiland-Jørgensen
2016-09-30 13:08 ` Neil Shepperd
2016-09-30 19:42 ` Dave Täht
2016-09-30 20:37 ` Neil Shepperd
2016-09-30 21:10 ` Dave Täht
2016-10-03 21:17 ` Neil Shepperd
2016-10-04 6:33 ` Henning Rogge
2016-10-04 16:09 ` Dave Täht
2016-10-20 5:56 ` Neil Shepperd
2016-09-27 17:52 ` Jonathan Morton
2016-09-27 18:18 ` Dave Taht
2016-09-27 18:56 ` Jonathan Morton [this message]
2016-09-27 19:29 ` Dave Taht
2016-09-27 19:54 ` Jonathan Morton
2016-09-28 23:26 ` Dave Taht
2016-09-28 23:34 ` Jonathan Morton
2016-09-29 20:43 ` Andrew Shewmaker
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=27B5A7E3-203D-468F-B487-BFFC9294D857@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.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