From: Jonathan Morton <chromatix99@gmail.com>
To: David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Computer generated congestion control
Date: Fri, 3 Apr 2015 12:28:04 +0300 [thread overview]
Message-ID: <CAJq5cE0wvZ7PL3yUPw1Y-gW-OGEY=Tt8oLkgYyzLrRcvLv=UfQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1504030137550.26044@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
> > I'd like them to put some sane upper bound on the RTT - one compatible
with satellite links, but which would avoid flooding unmanaged buffers to
multi-minute delays.
> The problem is that there aren't any numbers that meet these two criteria.
> Even if you ignore 10G and faster interfaces, a 1Gb/s interface
withsatellite sized latencies is a LOT of data, far more than is needed to
flood a 'normal' link
I very deliberately said "RTT", not "BDP". TCP stacks already track an
estimate of RTT for various reasons, so in principle they could stop
increasing the congestion window when that RTT reaches some critical value
(1 second, say). The fact that they do not already do so is evidenced by
the observations of multi-minute induced delays in certain circumstances.
And this is not a complete solution by any means. Vegas proved that an
altruistic limit on RTT by an endpoint, with no other measures within the
network, leads to poor fairness between flows. But if the major OSes did
that, more networks would be able to survive overload conditions while
providing some usable service to their users.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1277 bytes --]
next prev parent reply other threads:[~2015-04-03 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 6:42 Simon Barber
2015-04-03 7:45 ` Jonathan Morton
2015-04-03 8:52 ` David Lang
2015-04-03 9:28 ` Jonathan Morton [this message]
2015-04-03 9:44 ` David Lang
2015-04-03 11:06 ` Jonathan Morton
2015-04-03 12:03 ` Dave Taht
2015-04-04 23:33 ` Juliusz Chroboczek
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='CAJq5cE0wvZ7PL3yUPw1Y-gW-OGEY=Tt8oLkgYyzLrRcvLv=UfQ@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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