Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	 BBR Development <bbr-dev@googlegroups.com>
Subject: Re: [Cerowrt-devel] [bbr-dev] taking apart BBR's behaviors in flent
Date: Wed, 21 Sep 2016 15:45:28 -0400	[thread overview]
Message-ID: <CADVnQy=qUYquCCqayWoWQsWNOJ5w1dN7K5pLc40AycoHuX-XNA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Y=6rJKuFK3N5zMpw-LrMz4ta1jB6UD2Cg07xw8OfQpg@mail.gmail.com>

On Wed, Sep 21, 2016 at 3:25 PM, Dave Taht <dave.taht@gmail.com> wrote:
> > So it seems my intuition was wrong, at least for these scenarios. It wasn't
> > CUBIC that would kill BBR, it's the other way around.
>
> My intuition was that "delay based TCPs can't work on the internet!" -
> and was wrong, also.

Keep in mind that BBR is not really "delay-based", at least in the
traditional sense. BBR is not based on backing off in response to a
single signal like loss or RTT increases. If BBR could be said to be
"based" on any one thing, it's "model-based": it has a model of the
network with two parameters: bottleneck bandwidth and round-trip
propagation time. So delay increases do not always lead to a slower
sending rate or lower volume of data in flight. For example, if the
round-trip propagation delay increases but the bandwidth stays
constant, BBR can actually increase the amount of data in flight in
order to achieve its fair share of the bandwidth available in the
longer pipe.

Thanks for all this testing!

neal

  reply	other threads:[~2016-09-21 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 19:25 [Cerowrt-devel] " Dave Taht
2016-09-21 19:45 ` Neal Cardwell [this message]
2016-09-22  0:09 ` Dave Taht
2016-09-22 12:09 ` Alan Jenkins
2016-09-26 19:02   ` [Cerowrt-devel] [bbr-dev] " 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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADVnQy=qUYquCCqayWoWQsWNOJ5w1dN7K5pLc40AycoHuX-XNA@mail.gmail.com' \
    --to=ncardwell@google.com \
    --cc=bbr-dev@googlegroups.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=swmike@swm.pp.se \
    /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