Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Andrew Shewmaker <agshew@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] cake for net-next 4.8
Date: Thu, 29 Sep 2016 14:43:40 -0600	[thread overview]
Message-ID: <CAF-E8XHTpSXJxLRRa=NMn5q58s5J2yfbv-O5oEzQaqDy0OMETg@mail.gmail.com> (raw)
In-Reply-To: <6D370F33-92FF-42D0-AE6F-3425AE9DAFA3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

On Wed, Sep 28, 2016 at 5:34 PM, Jonathan Morton <chromatix99@gmail.com>
wrote:

>
> > On 29 Sep, 2016, at 02:26, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > All along I'd been assuming
> > that a specialized TCP of some new flavor yet-to-be-agreed-upon would
> > negotiate ECN and most/all its packets would be marked ECT(1), rather
> > than ECT(0), and a new AQM would treat a flow like that differently,
> > but still mark that flow with a CE that the endpoint would interpret
> > differently.
> >
> > Are you saying ECT(1) would, instead, be used as a "weaker or harder" CE?
>
> The former appears to be the solution TCP Prague are keen on.  It doesn’t
> seem like a robust, deployable solution to me, despite the tremendous
> amount of effort that’s gone into that class of solutions.
>
> The latter is my suggestion - to use the distinction between ECT(0) and
> ECT(1) as a hint, rather than a command, to slow down.  I also think we
> should move computation of the congestion window to the receiver, as that
> greatly simplifies the reverse-path signalling problem.
>

I agree that there's some big potential advantages to that. But I wouldn't
say the congestion window calculation should be moved to the receiver, so
much as duplicated by the receiver. Here's a link to a receiver-side
congestion control patch I've been working on:

https://github.com/systemslab/tcp_inigo/tree/master/inigo_receiver

It uses TCP timestamps to keep track of the accumulated differences in one
way delays, and adjusts the receive window similarly to DCTCP.

The mininet tests I've run show some promise making CUBIC and Reno share
more fairly and tightening up their RTT distribution, but I need to do a
lot more testing.

I'm looking forward to Eric Dumazet's usec resolution time stamp support
being upstreamed so that my receiver-side technique might become useful in
data centers.


> You may remember my description of ELR.  I started documenting it more
> formally, and then got distracted by something more urgent...
>
>  - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>



-- 
Andrew Shewmaker

[-- Attachment #2: Type: text/html, Size: 4156 bytes --]

      reply	other threads:[~2016-09-29 20:44 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
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 [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='CAF-E8XHTpSXJxLRRa=NMn5q58s5J2yfbv-O5oEzQaqDy0OMETg@mail.gmail.com' \
    --to=agshew@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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