General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] TCP BBR paper is now generally available
Date: Thu, 8 Dec 2016 09:24:38 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1612080923010.1747@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7DfMY4qHnbxYDUN8hfpgY_aNxa1LcyPKd6pa93qXe2Kw@mail.gmail.com>

On Fri, 2 Dec 2016, Dave Taht wrote:

> http://queue.acm.org/detail.cfm?id=3022184

"BBR converges toward a fair share of the bottleneck bandwidth whether 
competing with other BBR flows or with loss-based congestion control."

That's not what I took away from your tests of having BBR and Cubic flows 
together, where BBR just killed Cubic dead.

What has changed since? Have you re-done your tests with whatever has 
changed, I must have missed that? Or did I misunderstand?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  parent reply	other threads:[~2016-12-08  8:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 15:52 Dave Taht
2016-12-02 19:15 ` Aaron Wood
2016-12-02 20:32   ` Jonathan Morton
2016-12-02 22:22     ` Neal Cardwell
2016-12-02 22:40       ` Steinar H. Gunderson
2016-12-02 23:31         ` Eric Dumazet
2016-12-03 13:03           ` Neal Cardwell
2016-12-03 19:13             ` Steinar H. Gunderson
2016-12-03 20:20               ` Eric Dumazet
2016-12-03 20:26                 ` Jonathan Morton
2016-12-03 21:07                   ` Eric Dumazet
2016-12-03 21:34                     ` Steinar H. Gunderson
2016-12-03 21:50                       ` Eric Dumazet
2016-12-03 22:13                         ` Steinar H. Gunderson
2016-12-03 22:55                           ` Eric Dumazet
2016-12-03 23:02                             ` Eric Dumazet
2016-12-03 23:09                               ` Eric Dumazet
2016-12-03 23:03                             ` Steinar H. Gunderson
2016-12-03 23:15                               ` Eric Dumazet
2016-12-03 23:24                                 ` Eric Dumazet
2016-12-04  3:18                                   ` Neal Cardwell
2016-12-04  8:44                                   ` Steinar H. Gunderson
2016-12-04 17:13                                     ` Eric Dumazet
2016-12-04 17:38                                       ` Steinar H. Gunderson
2016-12-06 17:20                                   ` Steinar H. Gunderson
2016-12-06 21:31                                     ` Neal Cardwell
2016-12-03 21:38                     ` Jonathan Morton
2016-12-03 21:33                 ` Steinar H. Gunderson
2016-12-07 16:28               ` Alan Jenkins
2016-12-07 16:47                 ` Steinar H. Gunderson
2016-12-07 17:03                   ` Alan Jenkins
2016-12-08  8:24 ` Mikael Abrahamsson [this message]
2016-12-08 13:22   ` Dave Täht
2016-12-08 14:01     ` Mikael Abrahamsson
2016-12-08 21:29       ` Neal Cardwell
2016-12-08 22:31         ` Yuchung Cheng
2016-12-09 14:52           ` Klatsky, Carl

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/bloat.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.1612080923010.1747@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@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