From: Erkki Lintunen <ebirdie@iki.fi>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] BBR congestion control
Date: Sat, 17 Sep 2016 21:24:24 +0300 [thread overview]
Message-ID: <20160917182424.GA28071@radio2.ebirdie> (raw)
This may already be yesterday news to list subscribers, but may there be
still be others like me missing this fascinating new entry, I'm for
rescue.
<https://patchwork.ozlabs.org/patch/671069/>
> While it is impossible to disambiguate any single bandwidth or RTT
> measurement, a connection's behavior over time tells a clearer
> story. BBR uses a measurement strategy designed to resolve this
> ambiguity. It combines these measurements with a robust servo loop
> using recent control systems advances to implement a distributed
> congestion control algorithm that reacts to actual congestion, not
> packet loss or transient queue delay, and is designed to converge with
> high probability to a point near the optimal operating point.
Got the bit from Steinar H. Gunderson's blog,
<https://blog.sesse.net/blog/tech/2016-09-16-23-16_bbr_opensourced.html>,
where before he has shared his troubles with bufferbloat while delivering video
streams from big events of young hackers.
reply other threads:[~2016-09-17 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160917182424.GA28071@radio2.ebirdie \
--to=ebirdie@iki.fi \
--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