General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Computer generated congestion control
Date: Fri, 3 Apr 2015 01:52:14 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1504030137550.26044@nftneq.ynat.uz> (raw)
In-Reply-To: <CAJq5cE1=CrZS5zTNNcfSQuC=yrCpvhSrurOriTbpuhAe3D-Hvg@mail.gmail.com>

[-- Attachment #1: Type: TEXT/Plain, Size: 2115 bytes --]

On Fri, 3 Apr 2015, Jonathan Morton wrote:

> 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

Even if you "assume" that a satellite link is never going to be faster than say 
100Mb/s, with 1s of RTT you have more than enough data to drive a small link 
into delays long enough to start triggering retransmission of packets. and 
that's assuming that you have your queues defined by byte count, not packet 
count (which adds another large multiplier based on the potential need to hold 
enough tiny packets to keep the link busy)

Then when you add in the fact that the download side is being generated by a 
server that legitimately coudl have a 10Gb/sec or faster pipe, and while it may 
not need to talk over a satellite at those speeds, even a terrestrial pipe 
around the world has a high enough latency to require a bandwidth-latency 
product to rivel or exceed the worst-case consumer satellite situation...

In addition, even if the buffers are byte-based and tuned for exactly the pipe 
size, you still have the firness problem. Sparse/short flows tend to be things 
that are much mroe sensitive to latency (DNS, HTMl pages that then trigger the 
loading of many resoruces, etc) so you really do not want to have them waiting 
behind bulk data flows. Since you can't trust any QoS markings set by someone 
else, it's not possible to statically configure things to 'just work'. The good 
news is that we now have a few different ways of activly managng the queues that 
work well, so we can move from figuring otu what to do to trying to convince 
peopel to do it.

If it really was as simple as there beign a reasonable cap, and beng able to get 
unabiguous congestion signals reliably, the problesm would have been solved 
years ago

David Lang

[-- Attachment #2: Type: TEXT/PLAIN, Size: 140 bytes --]

_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2015-04-03  8:52 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 [this message]
2015-04-03  9:28     ` Jonathan Morton
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=alpine.DEB.2.02.1504030137550.26044@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.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