From: Jonathan Morton <chromatix99@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: Dave Taht <dave.taht@gmail.com>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
flent-users <flent-users@flent.org>
Subject: Re: [Ecn-sane] [bbr-dev] duplicating the BBRv2 tests at iccrg in flent?
Date: Fri, 5 Apr 2019 19:20:00 +0300 [thread overview]
Message-ID: <3EDC8EAC-1EB2-4E64-8973-8AE177D8789C@gmail.com> (raw)
In-Reply-To: <CADVnQy=DfST=dHFkZg9EeQRL0OH9HOqgRfJ0uWgUu4fBLD9tSA@mail.gmail.com>
> On 5 Apr, 2019, at 6:10 pm, 'Neal Cardwell' via BBR Development <bbr-dev@googlegroups.com> wrote:
>
> Right. I didn't mean setting the codel target to 242us. Where the slide says "Linux codel with ECN ce_threshold at 242us sojourn time" I literally mean a Linux machine with a codel qdisc configured as:
>
> codel ce_threshold 242us
I infer from this that BBR's new ECN support won't work properly with standard CE marking behaviour, only with the sort of signal that DCTCP requires. Is that accurate?
SCE allows providing that sort of high-fidelity congestion signal without losing interoperability with RFC-3168 compliant flows.
- Jonathan Morton
next prev parent reply other threads:[~2019-04-05 16:20 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 [this message]
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
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=3EDC8EAC-1EB2-4E64-8973-8AE177D8789C@gmail.com \
--to=chromatix99@gmail.com \
--cc=bbr-dev@googlegroups.com \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=flent-users@flent.org \
--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