From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] Fwd: [bbr-dev] Re: BBRv2 v2alpha branch rebased from 5.4 to 5.10, supports all CCs and E2 GCE VMs
Date: Tue, 19 Jan 2021 22:03:42 -0800 [thread overview]
Message-ID: <CAA93jw6n7x5Cu7n-ZASM9GTQvkF64Q3Du9XGUFfqjB6Hz6J5Xw@mail.gmail.com> (raw)
In-Reply-To: <B9B4ECF5-3375-44C3-BA61-7370114E3150@gmail.com>
On Fri, Jan 15, 2021 at 5:19 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 16 Jan, 2021, at 1:51 am, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > what's the state of SCE nowadays? Has anyone ported it to bbrv2 yet?
>
> We haven't attempted to do anything with BBR yet, instead trusting that any results using conventional AQM and/or L4S will translate reasonably easily. Instead we're focusing on conventional window-based algorithms, getting the reference qdiscs right, and pointing out enough flaws in L4S so that it stops being an obstacle to IETF progress.
It would be really nice to compared bbrv2 instances. But I've been
saying that since the beginning.
> We *have* got a big vote of confidence in the form of funding from both RIPE and NGI Pointer. That gives us time and freedom to work on SCE without too many unnecessary distractions. One of the things we're doing with that is building a decent test harness.
Very happy to see that.
The thing is, so far as I know, the basic brick-wall aspect of the aqm
hasn't changed much, especially when FQ is involved, have the aqm
implemantations changed at all for SCE?
> - Jonathan Morton
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
prev parent reply other threads:[~2021-01-20 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADVnQymBywmgWEqYHs9xaX2Em5bYNjmn7yN9qTvYqL=HwT4gLA@mail.gmail.com>
[not found] ` <CADVnQym7fxYpvC=h38Ga9ORWsOXcS2Mk3jUecKWtBSc7+neEUw@mail.gmail.com>
2021-01-15 23:51 ` Dave Taht
2021-01-16 1:19 ` Jonathan Morton
2021-01-20 6:03 ` Dave Taht [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/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=CAA93jw6n7x5Cu7n-ZASM9GTQvkF64Q3Du9XGUFfqjB6Hz6J5Xw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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