From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
"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:32:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1609211329370.1477@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5t0au0P03nnPhy2nh9RWObrRr9SgWBtEiq8kfO8XTiRw@mail.gmail.com>
On Wed, 21 Sep 2016, Dave Taht wrote:
> I did a fairly comprehensive string of tests today, comparing it at
> 20Mbits, 48ms RTT, to cubic and competing with cubic, against a byte
> fifo of 256k, pie, cake, cake flowblind, and fq_codel.
20 megabit/s is 2.5 megabyte/s, so that 256k FIFO is only 100ms worth of
buffering. I guess you see packet drop in steady state here, ie buffer is
full?
I'd be interested in seeing same experiment start with 10MB FIFO, and
having CUBIC flow start first and give it proper head start.
My intuition and understanding of what's going to happen might very well
be completely off, but I think it'd be interesting to know.
I'll take a look at your flent data, thanks for posting them!
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-09-21 11:32 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
2016-09-21 11:19 ` Dave Taht
2016-09-21 11:32 ` Mikael Abrahamsson [this message]
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.1609211329370.1477@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--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