From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] Fwd: [bbr-dev] Re: Applying BBRv2 patches
Date: Mon, 18 Mar 2019 02:26:35 -0700 [thread overview]
Message-ID: <CAA93jw5Du8aAFPvq5OdXVidcRDbMpa9=CuXEaj3BO3m5LdFhTg@mail.gmail.com> (raw)
In-Reply-To: <CADVnQykOm-kPVAbvL2H4O-6e-z38Gz3Fd96RhSeaSX7d08w9-A@mail.gmail.com>
---------- Forwarded message ---------
From: 'Neal Cardwell' via BBR Development <bbr-dev@googlegroups.com>
Date: Fri, Mar 15, 2019 at 12:18 PM
Subject: Re: [bbr-dev] Re: Applying BBRv2 patches
To: Jeremy Payne <jp557198@gmail.com>
Cc: BBR Development <bbr-dev@googlegroups.com>
Hi,
The enhancements that we have been calling "BBR v2" are still under
testing, and have not been posted yet. For BBR v2, we sketched out an
overview and some lab test results at IETF 102 (links here). We'll be
giving a quick update about that effort at the ICCRG session at IETF
104 in a few weeks.
For Linux TCP BBR, the most recent upstream patches of interest are
for improving performance with high degrees of aggregation (as in
wifi, cellular, cable modems, LRO/GRO, etc) on low-RTT paths. The
biggest impacts we have seen are cases with wifi links where the
two-way propagation delay is in the range 1-10ms, so that would be a
scenario to start with, for testing. Those patches are discussed here:
https://groups.google.com/d/msg/bbr-dev/kBZaq98xCC4/5EUi7c3MCgAJ
Keep in mind those patches are not in 5.0.2. They will be in 5.1, or
if you have the option of building custom kernels then you can
cherry-pick them on top of your 5.0.2.
thanks,
neal
On Fri, Mar 15, 2019 at 11:34 AM Jeremy Payne <jp557198@gmail.com> wrote:
>
> Hello,
>
> I've been following developments here, and I'm now considering soaking BBR on one of our production machines.
> Question is, it seems there are some outstanding issues with BBR that may affect network/application response times.
> Before soaking in production, are there any suggested tests I can run in the lab that show performance impacts without the
> BBR2 patches, and then show performance improvements with the BBR2 patches?
>
> Primary use case is live MPEG-DASH/HLS video delivery.
>
> I plan on testing against a kernel that doesnt contain these patches, 4.14.106, and a kernel that looks to contain most of the BBR2 patches, 5.0.2
>
> Thanks!
>
>
> On Wednesday, March 13, 2019 at 12:09:22 AM UTC-5, Jared Newman wrote:
>>
>> Hey BBR-dev,
>>
>> I'm trying to apply the patches given in https://groups.google.com/forum/#!topic/bbr-dev/8pgyOyUavvY, but am struggling to find what commit of next-net I should apply them on. I tried a couple different tags in https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git but would always get conflicts that I didn't feel comfortable resolving. Does anyone have a suggestion / commit hash to apply them to?
>>
>> Cheers,
>> Jared.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2019-03-18 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <189cdc56-9eff-4a9f-aee1-1eea06d78664@googlegroups.com>
[not found] ` <CADVnQy=EtxtePAcdXu77=nbgENfR-Uqr_ZtMqX9r5XmufbY2tQ@mail.gmail.com>
2019-03-18 9:24 ` [Ecn-sane] Fwd: [bbr-dev] " Dave Taht
[not found] ` <0d5b5f96-ec5d-4055-9cdc-7b650dbb7ea5@googlegroups.com>
[not found] ` <CADVnQymWkbZXA5ssrP8dh2yyDw21z5EnsHC7VriAFgpQRZHBjA@mail.gmail.com>
[not found] ` <567ee54b-3cad-4e65-9803-d4a7f0553adc@googlegroups.com>
2019-03-18 9:26 ` [Ecn-sane] " Dave Taht
[not found] ` <1da4d9e4-13f9-4767-9519-93978664c79b@googlegroups.com>
[not found] ` <CADVnQykOm-kPVAbvL2H4O-6e-z38Gz3Fd96RhSeaSX7d08w9-A@mail.gmail.com>
2019-03-18 9:26 ` 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='CAA93jw5Du8aAFPvq5OdXVidcRDbMpa9=CuXEaj3BO3m5LdFhTg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=make-wifi-fast@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