From: d@taht.net (Dave Täht)
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] First draft of complete "Bufferbloat And You" enclosed.
Date: Thu, 10 Feb 2011 10:50:04 -0700 [thread overview]
Message-ID: <87lj1n3hkj.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <4D53FC4B.5000307@freedesktop.org> (Jim Gettys's message of "Thu, 10 Feb 2011 09:55:07 -0500")
Jim Gettys <jg@freedesktop.org> writes:
> Well, another way to think about transport protocols is as servo
> systems, that apply feedback to control the rates.
>
> If you look at the TCP traces that set me off on this merry chase, you
> see quite violent periodic behaviour, where the periods are quite long
> (of order 10 seconds).
>
> Injecting delays way beyond the natural RTT is hazardous to the
> stability of transport protocols.
>
> You can see TCP slowly losing its mind it's RTT estimation gets longer
> and longer as the buffer fills. Eventually, it goes ballistic.
>
> The servo system's stability has been destroyed...
I LIKE the idea of trying to think about this as a complex servo system.
I also like many of the other analogies that have gone by.
At the moment, the lower levels of plumbing in the internet's servos
more closely resemble a rube goldberg machine.
Everybody here could use a belly laugh. Try this:
http://www.youtube.com/watch?v=qybUFnY7Y8w
We've also been overcomplicating this discussion, getting overwhelmed in
detail.
There is no perfect analogy, all we can do is - as blind men feeling up
this elephant from trunk, hip and tail - is to keep trying to describe
its shape in as many different ways as possible until it's more than a
shadow on the wall... [1]
If we can take a step back and not go for one-size-fits all and think of
each audience that we need to address, perhaps we'll keep finding
analogies that work for each audience in smaller, more digestible, pieces.
> - Jim
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[1] Plato and the Elephant - coming soon to a writers workshop near you!
--
Dave Taht
http://nex-6.taht.net
next prev parent reply other threads:[~2011-02-10 17:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 13:23 Eric Raymond
2011-02-05 13:42 ` Jim Gettys
2011-02-05 15:12 ` Dave Täht
2011-02-05 15:46 ` Dave Täht
2011-02-06 13:37 ` Eric Raymond
2011-02-05 17:56 ` richard
2011-02-05 19:48 ` richard
2011-02-05 22:12 ` Dave Täht
2011-02-06 1:29 ` richard
2011-02-06 2:35 ` Dave Täht
2011-02-06 2:50 ` richard
2011-02-08 15:17 ` Justin McCann
2011-02-08 18:18 ` Eric Raymond
2011-02-08 18:31 ` richard
2011-02-08 18:50 ` Bill Sommerfeld
2011-02-09 15:50 ` Eric Raymond
2011-02-08 20:10 ` Sean Conner
2011-02-09 4:24 ` Justin McCann
2011-02-10 14:55 ` Jim Gettys
2011-02-10 17:50 ` Dave Täht [this message]
2011-02-08 19:43 ` Juliusz Chroboczek
2011-02-08 19:52 ` richard
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=87lj1n3hkj.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/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