From: Venkat Arun <venkatarun95@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
venkatar@csail.mit.edu,
Mohammad Alizadeh <alizadeh@csail.mit.edu>,
Hari Balakrishnan <hari@csail.mit.edu>
Subject: Re: [Bloat] SIGCOMM MIT paper: Starvation in e2e congestion control
Date: Sun, 7 Aug 2022 09:58:31 +0530 [thread overview]
Message-ID: <CADacQHax-vT8h==mV=pYs7TnYCGrwv_spSx2RAc0xv6k4UnLmQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7K8kP2ZnsvuACizii=zvxR24gU3rKbn-__R2LWF1WK6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Hi Dave,
Yes definitely, when fair-queuing is present, the onus is no longer on the
congestion control algorithm to ensure fairness. In fact, if buffer-sharing
is implemented correctly, FQ can even stand against adversarial congestion
control algorithms. We have good reason to believe that end-to-end
congestion control algorithms can provably work (i.e. achieve high
utilization, bounded delay and fairness) in the presence of FQ.
Cheers,
Venkat
On Fri, Aug 5, 2022 at 12:36 AM Dave Taht <dave.taht@gmail.com> wrote:
> 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
>
[-- Attachment #2: Type: text/html, Size: 2185 bytes --]
prev parent reply other threads:[~2022-08-07 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 19:05 Dave Taht
2022-08-07 4:28 ` Venkat Arun [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADacQHax-vT8h==mV=pYs7TnYCGrwv_spSx2RAc0xv6k4UnLmQ@mail.gmail.com' \
--to=venkatarun95@gmail.com \
--cc=alizadeh@csail.mit.edu \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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