Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] BBR congestion control algorithm for TCP in net-next
Date: Sat, 17 Sep 2016 20:34:45 +0200	[thread overview]
Message-ID: <CAMZR1YDj_QB3sE1VXbn0GCUYF072x-E2DFVXSAKSgW1uTja_OQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

Hi,

Just saw this: https://patchwork.ozlabs.org/patch/671069/

Interested to see how BBR would play out with things like fq_codel or cake.

"loss-based congestion control is unfortunately out-dated in today's
networks. On
today's Internet, loss-based congestion control causes the infamous
bufferbloat problem"

So, instead of waiting for packet loss they probe and measure, e.g. when
doing slow start (here called STARTUP) they don't speed up until packet
loss, but slow down before reaching estimated bandwidth level.

Cake and fq_codel work on all packets and aim to signal packet loss early
to network stacks by dropping; BBR works on TCP and aims to prevent packet
loss.


Best regards,
Maciej

[-- Attachment #2: Type: text/html, Size: 999 bytes --]

             reply	other threads:[~2016-09-17 18:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 18:34 Maciej Soltysiak [this message]
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
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=CAMZR1YDj_QB3sE1VXbn0GCUYF072x-E2DFVXSAKSgW1uTja_OQ@mail.gmail.com \
    --to=maciej@soltysiak.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