From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Cc: venkatar@csail.mit.edu,
Mohammad Alizadeh <alizadeh@csail.mit.edu>,
Hari Balakrishnan <hari@csail.mit.edu>
Subject: [Starlink] SIGCOMM MIT paper: Starvation in e2e congestion control
Date: Thu, 4 Aug 2022 12:05:39 -0700 [thread overview]
Message-ID: <CAA93jw7K8kP2ZnsvuACizii=zvxR24gU3rKbn-__R2LWF1WK6Q@mail.gmail.com> (raw)
Perhaps it's obvious to the authors that FQ opens up new possibilities
for delay based convergence. Otherwise, pretty good:
"We prove that when two flows using the same CCA share a bottleneck
link, if the non-congestive delay variations exceed double the
difference between the maximum and minimum queueing delay at
equilibrium, then there are patterns of non-congestive delay where one
flow will get arbitrarily low throughput compared to the other. Our
theorem shows that CCAs have
to choose at most two out of three properties: high through put,
convergence to a small and bounded delay range, and no starvation."
Paper: http://people.csail.mit.edu/venkatar/cc-starvation.pdf
Article: https://news.mit.edu/2022/algorithm-computer-network-bandwidth-0804
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2022-08-04 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 19:05 Dave Taht [this message]
2022-08-07 4:28 ` Venkat Arun
[not found] <mailman.3.1659715201.24001.starlink@lists.bufferbloat.net>
2022-08-08 21:39 ` David P. Reed
2022-08-08 22:37 ` David Lang
2022-08-08 22:41 ` Dave Taht
2022-08-11 14:29 ` Hesham ElBakoury
2022-08-17 21:34 ` Dave Taht
[not found] <mailman.562.1660228174.1281.starlink@lists.bufferbloat.net>
2022-08-11 19:34 ` David P. Reed
2022-08-11 20:22 ` Ulrich Speidel
2022-08-11 20:24 ` Ulrich Speidel
2022-08-12 14:21 ` Livingood, Jason
2022-08-12 14:23 ` Hesham ElBakoury
2022-08-25 20:26 ` Dave Taht
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7K8kP2ZnsvuACizii=zvxR24gU3rKbn-__R2LWF1WK6Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=alizadeh@csail.mit.edu \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hari@csail.mit.edu \
--cc=starlink@lists.bufferbloat.net \
--cc=venkatar@csail.mit.edu \
/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