Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	flent-users <flent-users@flent.org>,
	BBR Development <bbr-dev@googlegroups.com>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Flent-users] [bbr-dev] duplicating the BBRv2 tests at iccrg in flent?
Date: Tue, 9 Apr 2019 05:09:29 +0300	[thread overview]
Message-ID: <08179F6A-A432-4465-BF70-BE8D727436C8@gmail.com> (raw)
In-Reply-To: <CADVnQy=xLA19j1z_AvvUmLhVgWepkpujvkn=bKXt+_1uEzai8A@mail.gmail.com>

> I wonder if one is willing to change ECN semantics already, by making CELighter weight than a packetdrop, why not also using an explicit signal for emergency brake?

This is the principle I proposed with SCE.  There, CE remains a broadly drop-equivalent signal (the "emergency brake"), while ECT(1) becomes SCE, a softer and higher-precision signal which is produced in the way DCTCP expects.

As of a couple of hours ago, I have three machines in my bedroom which are running SCE-aware Linux kernels, including a "rehabilitated" version of DCTCP which responds appropriately to drops, CE and SCE and is therefore compatible with use on the general Internet.

Now I just need to blow the cobwebs off the test harnesses which were used to refine Cake, to ensure that the assertion I just made above is actually true.

 - Jonathan Morton

  reply	other threads:[~2019-04-09  2:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05  7:42 [Ecn-sane] " Dave Taht
2019-04-05 15:10 ` [Ecn-sane] [bbr-dev] " Neal Cardwell
2019-04-05 15:51   ` Dave Taht
2019-04-05 16:58     ` Neal Cardwell
2019-04-05 16:20   ` Jonathan Morton
2019-04-06 11:56     ` Neal Cardwell
2019-04-06 14:37       ` [Ecn-sane] [Flent-users] " Sebastian Moeller
2019-04-09  1:33         ` Neal Cardwell
2019-04-09  2:09           ` Jonathan Morton [this message]
2019-04-09  6:30           ` Sebastian Moeller
2019-04-09 14:33             ` Neal Cardwell
2019-04-09 17:20               ` Sebastian Moeller
2019-04-06 11:49   ` [Ecn-sane] " Dave Taht
2019-04-06 12:31     ` Neal Cardwell

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=08179F6A-A432-4465-BF70-BE8D727436C8@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=flent-users@flent.org \
    --cc=moeller0@gmx.de \
    --cc=ncardwell@google.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