From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] BBR congestion control algorithm for TCP in net-next
Date: Wed, 21 Sep 2016 12:15:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1609211210280.1477@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5hR7bjxYNgzWQOSAtKWG+0oUGLFk+dmvmSMgkx5YTzuA@mail.gmail.com>
On Wed, 21 Sep 2016, Dave Taht wrote:
> I dunno, I'm just reading tea leaves here!
>
> can't wait for the paper!
+1.
I would like to understand how BBR interacts with a window-fully-open
classic TCP session and FIFO induced delay that is in steady-state before
the BBR session starts.
So let's say I have 100ms of lightspeed-in-fiber RTT, and I am then
running a file transfer with some other TCP algorithm which is sitting
there, window fully open, creating an additional 100ms of
stupid-router-FIFO-buffering delay.
So new BBR TCP session comes along, sees 200ms of RTT, and starts sending.
I guess the classic TCP algorithm still keeps its window fully open, and
doesn't care that RTT now increased to 210ms by the BBR flow packets.
Now what? BBR flow sees increased latency, and backs off, right? So how
much of the bandwidth will each flow get? How do these interact?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-09-21 10:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 18:34 Maciej Soltysiak
2016-09-17 18:53 ` Dave Taht
2016-09-21 9:06 ` Alan Jenkins
2016-09-21 9:39 ` Dave Taht
2016-09-21 10:10 ` Alan Jenkins
2016-09-21 10:15 ` Mikael Abrahamsson [this message]
2016-09-21 11:14 ` Alan Jenkins
2016-09-21 11:28 ` Mikael Abrahamsson
2016-09-21 11:19 ` Dave Taht
2016-09-21 11:32 ` Mikael Abrahamsson
2016-09-21 12:40 ` Mikael Abrahamsson
2016-09-21 13:49 ` [Cerowrt-devel] [Bloat] " Alan Jenkins
2016-09-17 20:11 ` [Cerowrt-devel] " Jonathan Morton
2016-09-26 18:47 ` Aaron Wood
2016-09-26 19:30 ` Neal Cardwell
2016-09-26 19:45 ` Aaron Wood
2016-09-26 21:38 ` Dave Taht
2016-09-26 22:09 ` Aaron Wood
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=alpine.DEB.2.02.1609211210280.1477@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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