From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Yuchung Cheng <ycheng@google.com>
Cc: BBR Development <bbr-dev@googlegroups.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [bbr-dev] Re: "BBR" TCP patches submitted to linux kernel
Date: Wed, 2 Nov 2016 10:27:08 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1611021015380.14320@uplift.swm.pp.se> (raw)
In-Reply-To: <CAK6E8=eCBzLxnmEvq5h5yggCbiX_F4whrE1EG6UMfO6Wq5SNRg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 734 bytes --]
On Tue, 1 Nov 2016, Yuchung Cheng wrote:
> We are curious why you choose the single-queued AQM. Is it just for the
> sake of testing?
Non-flow aware AQM is the most commonly deployed "queue management" on the
Internet today. Most of them are just stupid FIFOs with taildrop, and the
buffer size can be anywhere from super small to huge depending on
equipment used and how it's configured.
Any proposed TCP congestion avoidance algorithm to be deployed on the
wider Internet has to some degree be able to handle this deployment
scenario without killing everything else it's sharing capacity with.
Dave Tähts testing case where BBR just kills Cubic makes me very
concerned.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2016-11-02 9:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 21:04 [Bloat] " Dave Taht
2016-09-16 21:11 ` Steinar H. Gunderson
2016-09-16 21:14 ` Eric Dumazet
2016-09-16 22:29 ` Dave Taht
2016-09-29 11:24 ` Mário Sérgio Fujikawa Ferreira
2016-09-29 19:43 ` Dave Täht
2016-09-29 20:35 ` Aaron Wood
2016-09-30 8:12 ` Mikael Abrahamsson
2016-09-30 14:16 ` Aaron Wood
2016-09-29 21:23 ` Steinar H. Gunderson
2016-09-30 1:54 ` Mario Ferreira
2016-09-30 3:50 ` Dave Täht
2016-09-30 4:29 ` Aaron Wood
2016-09-29 23:26 ` Benjamin Cronce
2016-09-30 1:58 ` Mario Ferreira
2016-10-21 8:47 ` Steinar H. Gunderson
2016-10-21 10:28 ` Eric Dumazet
2016-10-21 10:42 ` Steinar H. Gunderson
2016-10-21 10:47 ` Steinar H. Gunderson
2016-10-21 10:55 ` Eric Dumazet
2016-10-21 10:52 ` Eric Dumazet
2016-10-21 11:03 ` Steinar H. Gunderson
2016-10-21 11:40 ` Eric Dumazet
2016-10-21 11:45 ` Steinar H. Gunderson
2016-10-27 17:04 ` Steinar H. Gunderson
2016-10-27 17:31 ` Eric Dumazet
2016-10-27 17:33 ` Dave Taht
2016-10-27 17:52 ` Eric Dumazet
2016-10-27 17:59 ` Dave Taht
2016-10-27 17:57 ` Yuchung Cheng
2016-10-27 18:14 ` Dave Taht
2016-10-27 21:30 ` [Bloat] [bbr-dev] " Yuchung Cheng
2016-11-01 23:13 ` Yuchung Cheng
2016-11-01 23:49 ` Jonathan Morton
2016-11-02 9:27 ` Mikael Abrahamsson [this message]
2016-11-02 17:21 ` Klatsky, Carl
2016-11-02 18:48 ` Dave Täht
2016-11-25 12:51 ` [Bloat] " Bernd Paysan
2016-10-21 10:50 ` Zhen Cao
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.1611021015380.14320@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ycheng@google.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