Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jared Newman <jnewman2501@gmail.com>
Cc: BBR Development <bbr-dev@googlegroups.com>,
	ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] [bbr-dev] Applying BBRv2 patches
Date: Mon, 18 Mar 2019 02:26:12 -0700	[thread overview]
Message-ID: <CAA93jw4uZhmqy5zW_yPQGQ+F2FErGU-4SYWcaWVC5cGCO5jo0w@mail.gmail.com> (raw)
In-Reply-To: <567ee54b-3cad-4e65-9803-d4a7f0553adc@googlegroups.com>

On Thu, Mar 14, 2019 at 11:21 AM Jared Newman <jnewman2501@gmail.com> wrote:
>
> Hey Neal,
>
> Just a quick update: turns out the 1-2 second delays we were seeing were because we had a net.ipv4.tcp_notsent_lowat of 4MB (!!). Setting this to 16KB made BBR perform beautifully on the link, and reduced all queue delays to within the expected RTT variance. I'm still keen on comparing BBR with and without these patches, so will report back shortly with these results.

I am a huge fan of this option, (apple has it too) and certainly the
default is far too high.

I would really love to have an equivalent net.ipv4.tcp_notsent_lowat
for udp sockets as well as a setsockopt. Has that happened yet?


> Cheers,
> Jared.
>
> On Tuesday, March 12, 2019 at 10:50:40 PM UTC-7, Neal Cardwell wrote:
>>
>> Thanks for the report! We'd be interested to hear how it goes.
>>
>> thanks,
>> neal
>>
>> On Tue, Mar 12, 2019 at 10:44 PM Jared Newman <jnewm...@gmail.com> wrote:
>>>
>>> Ah awesome, glad to see the improvements make it into the next kernel! Thanks for the pointers and quick response, Neal.
>>>
>>> We're running TCP BBR on a 2.4GHz mobile ad hoc network and are seeing an excessive outgoing queue build up, leading to application delays of 1-2 seconds on a link that has a BBR-estimated min-RTT of ~15ms. By the sounds of it, feature (2) will be what we want so we'll try applying the patches on top of 18845557fd6f and see how things go.
>>>
>>> Cheers,
>>> Jared.
>>>
>>> On Tuesday, March 12, 2019 at 10:29:08 PM UTC-7, Neal Cardwell wrote:
>>>>
>>>> Hi,
>>>>
>>>> For the patches in  https://groups.google.com/forum/#!topic/bbr-dev/8pgyOyUavvY there were two main features:
>>>>
>>>> (1) Higher throughput for wifi and other paths with aggregation
>>>>
>>>> (2) Lower queuing delays by frequently draining excess in-flight data
>>>>
>>>>
>>>> For the patches related to (1), that functionality is already in davem/net-next and torvalds/linux, as of recently, and those patches will be in Linux 5.1. We were waiting until Linux 5.1 is released to announce that on this e-mail list. But since it came up anyway, we may as well mention it. ;-)
>>>>
>>>>
>>>> For the patches related to (2), that functionality is still undergoing testing on YouTube and elsewhere.
>>>>
>>>>
>>>> If you want to apply the original patches from  https://groups.google.com/forum/#!topic/bbr-dev/8pgyOyUavvY  then you can apply them on top of the Linux commit:
>>>>
>>>> 18845557fd6f
>>>>
>>>> from March 2018. That's where they were originally generated.
>>>>
>>>>
>>>> best,
>>>>
>>>> neal
>>>>
>>>>
>>>>
>>>> On Tue, Mar 12, 2019 at 10:09 PM Jared Newman <jnewm...@gmail.com> 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+u...@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+u...@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

  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: " 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         ` Dave Taht [this message]
     [not found] ` <1da4d9e4-13f9-4767-9519-93978664c79b@googlegroups.com>
     [not found]   ` <CADVnQykOm-kPVAbvL2H4O-6e-z38Gz3Fd96RhSeaSX7d08w9-A@mail.gmail.com>
2019-03-18  9:26     ` [Ecn-sane] Fwd: [bbr-dev] " 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=CAA93jw4uZhmqy5zW_yPQGQ+F2FErGU-4SYWcaWVC5cGCO5jo0w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=jnewman2501@gmail.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