From: Aaron Wood <woody77@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Eric Dumazet <edumazet@google.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [Cerowrt-devel] BBR congestion control algorithm for TCP in net-next
Date: Mon, 26 Sep 2016 19:45:15 +0000 [thread overview]
Message-ID: <CALQXh-PNcgAEC=bocox4UL6Jr_vwxio2RaUf34e-OTbCosCzBA@mail.gmail.com> (raw)
In-Reply-To: <CADVnQynSJ9Ze2cXL=J21E9EO2QT37s-4NNW7x=XBVAF-4VY4mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
Thanks! And sorry that I missed the sample code in the patch.
On Mon, Sep 26, 2016 at 12:30 Neal Cardwell <ncardwell@google.com> wrote:
> On Mon, Sep 26, 2016 at 2:47 PM, Aaron Wood <woody77@gmail.com> wrote:
> > 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?
>
> Yes, you can use either approach:
>
> (1) from code you can use TCP_CC_INFO socket option; there is sample
> code in the original kernel patch for TCP_CC_INFO:
> https://patchwork.ozlabs.org/patch/465806/
>
> (2) from ss: if you download and build the net-next branch of the
> iproute2 package:
>
> http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/log/?h=net-next
> then you will get support to print out the main parameters for a BBR
> connection, eg:
>
> The patch with BBR support for ss is here:
>
> http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?h=net-next&id=2f0f9aef94129643133363b4503468cdccc481cc
>
> As the commit notes, the BBR output looks like:
> bbr:(bw:1.2Mbps,mrtt:18.965,pacing_gain:2.88672,cwnd_gain:2.88672)
>
> Hope that helps,
> neal
>
> >
> > -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
> >>
> >
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
[-- Attachment #2: Type: text/html, Size: 4183 bytes --]
next prev parent reply other threads:[~2016-09-26 19:45 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
2016-09-26 19:30 ` Neal Cardwell
2016-09-26 19:45 ` Aaron Wood [this message]
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-PNcgAEC=bocox4UL6Jr_vwxio2RaUf34e-OTbCosCzBA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--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