From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alan Jenkins <alan.christopher.jenkins@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 13:28:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1609211324281.1477@uplift.swm.pp.se> (raw)
In-Reply-To: <CANmMgnGtOevcNRvQPYaYcKcOXDNVVxW2PV36Gzy7Q_j5C36p9w@mail.gmail.com>
On Wed, 21 Sep 2016, Alan Jenkins wrote:
> That assumes the measured maximum bandwidth (over an interval of 10*rtt)
> remains constant. (Say there were 100 BBR flows, then you added one
> CUBIC flow to bloat the buffer). I don't have a good intuition for how
> the bandwidth estimation behaves in general.
My example was single CUBIC flow already existing, steady state, full
speed, filling pipe and buffer with 100ms of packets, and it's not filling
buffer to 110ms of packets because its window is full. There is no packet
loss currently.
Now you add single BBR flow. What happens, what's the ratio between BBR
and CUBIC after 20 seconds of letting things settle down to new
equilibrium?
Consider the FIFO buffer practically infinite, or at least able to buffer
5 seconds of packets without drop. It's an interface with a single,
stupid, huge FIFO buffer.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-09-21 11:28 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
2016-09-21 11:14 ` Alan Jenkins
2016-09-21 11:28 ` Mikael Abrahamsson [this message]
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.1609211324281.1477@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@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