From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] Fwd: [bbr-dev] Re: BBRv2 v2alpha branch rebased from 5.4 to 5.10, supports all CCs and E2 GCE VMs
Date: Fri, 15 Jan 2021 15:51:12 -0800 [thread overview]
Message-ID: <CAA93jw59=X15-HxTeh6jvsY7NUMod0ZgRBaq-9qVCGuPwCLbjQ@mail.gmail.com> (raw)
In-Reply-To: <CADVnQym7fxYpvC=h38Ga9ORWsOXcS2Mk3jUecKWtBSc7+neEUw@mail.gmail.com>
what's the state of SCE nowadays? Has anyone ported it to bbrv2 yet?
I was going to take a stab at D*....
---------- Forwarded message ---------
From: 'Neal Cardwell' via BBR Development <bbr-dev@googlegroups.com>
Date: Fri, Jan 15, 2021 at 3:29 PM
Subject: [bbr-dev] Re: BBRv2 v2alpha branch rebased from 5.4 to 5.10,
supports all CCs and E2 GCE VMs
To: BBR Development <bbr-dev@googlegroups.com>
Based on some quick feedback from the user community (thanks!) we have
fixed a few minor issues with yesterday's release, and pushed an
update to the v2alpha branch in the github repo. The fixes can be
found at the latest tagged release:
https://github.com/google/bbr/releases/tag/v2alpha-2021-01-15
The changes since yesterday's release:
(1) a bug fix for the warning that has been reported by a few users:
WARN_ON_ONCE(bbr->prior_cwnd == 0);
(2) a fix for a compilation error caused for users of the following
.config option:
CONFIG_BPF_SYSCALL=y
(3) enabled the .config option CONFIG_BPF_SYSCALL=y to catch further issues
of this kind
best,
neal
ps: as always, you can find the instructions to download and build
Linux TCP BBRv2 alpha here:
https://github.com/google/bbr/blob/v2alpha/README.md
On Thu, Jan 14, 2021 at 6:03 PM Neal Cardwell <ncardwell@google.com> wrote:
>
> Hi all,
>
> By popular demand, we have rebased the BBRv2 v2alpha branch from 5.4 to 5.10.
>
> The BBRv2 code in this release should be functionally identical to the previous release, since in this rebase we only made the minimal changes to the BBRv2 and TCP patches necessary to get the code to compile.
>
> There were two changes of note we incorporated during the rebase. The kernel .config generated by the gce-install.sh build/install/boot script now has some added features:
>
> (1) it builds all available congestion control modules, to facilitate comparisons (a request made recently on the bbr-dev list here)
>
> (2) it has UEFI support needed to allow booting on the new E2 "cost-optimized general purpose" VM type on Google Cloud
>
> You can find the list of rebased commits here.
>
> As always, previous versions of the v2alpha release can be found using the git tags in the Google bbr repository.
>
> best,
> neal
>
--
You received this message because you are subscribed to the Google
Groups "BBR Development" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to bbr-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbr-dev/CADVnQym7fxYpvC%3Dh38Ga9ORWsOXcS2Mk3jUecKWtBSc7%2BneEUw%40mail.gmail.com.
--
"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
next parent reply other threads:[~2021-01-15 23:51 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 [this message]
2021-01-16 1:19 ` Jonathan Morton
2021-01-20 6:03 ` Dave Taht
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='CAA93jw59=X15-HxTeh6jvsY7NUMod0ZgRBaq-9qVCGuPwCLbjQ@mail.gmail.com' \
--to=dave.taht@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