From: Aaron Wood <woody77@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: Mon, 26 Sep 2016 11:47:13 -0700 [thread overview]
Message-ID: <CALQXh-OCV5T1=ZczY+=snZfXqY1t7vYEMuMLGbUps0afP8t+Qg@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YDj_QB3sE1VXbn0GCUYF072x-E2DFVXSAKSgW1uTja_OQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
Dumb question on this: The tcp_bbr_info struct for a socket can be
inspected at runtime through the ss utility or through a get socket opts
call, right?
-Aaron
On Sat, Sep 17, 2016 at 11:34 AM, Maciej Soltysiak <maciej@soltysiak.com>
wrote:
> 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
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #2: Type: text/html, Size: 1950 bytes --]
next prev parent reply other threads:[~2016-09-26 18:47 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
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 [this message]
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='CALQXh-OCV5T1=ZczY+=snZfXqY1t7vYEMuMLGbUps0afP8t+Qg@mail.gmail.com' \
--to=woody77@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