From: Jim Gettys <jg@freedesktop.org>
To: esr@thyrsus.com
Cc: Eric Raymond <esr@snark.thyrsus.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Overview modifications
Date: Mon, 07 Feb 2011 14:56:47 -0500 [thread overview]
Message-ID: <4D504E7F.6030602@freedesktop.org> (raw)
In-Reply-To: <20110206202015.GA3004@thyrsus.com>
On 02/06/2011 03:20 PM, Eric Raymond wrote:
> Jim Gettys<jg@freedesktop.org>:
>>> Change in progress -- append to the "Hating" paragraph the following
>>> sentence: "Lossy networks such as wireless actually show less chaotic
>>> behavior under load than clean ones." Is this correct and adequate?
>>
>> It's not chaotic behaviour. In fact, it is much more worrying: it
>> is periodic (oscillatory) behaviour. Chaos is good, in this case.
>
> Dave also says my take is wrong and is promising to suggest a correction.
> I have enough other stuff to do that I'll wait on that.
>
>> My nightmare, is that as traffic shifts over more and more to
>> saturated links as XP retires, we end up with self synchronising
>> behaviour on a local, regional or global scale, and havoc ensues,
>> and parts/all of the Internet stop working. Whether these fears are
>> justified, I do not know.
>>
>> Think: we may be a column of soldiers in cadence approaching a bridge...
>
> New graphs at the end of "From Highway to Network":
>
> We also have some worries about the future. For various reasons
> (including the gradual retirement of Windows XP) more and more
> Internet traffic is now running over saturated links. In this new
> environment, we think there is a possibility that bufferbloat cascades
> and defects in management strategies might produce self-synchronising
> behaviour in network traffic - packet floods and network resonance on
> a local, regional or global scale that could be a greater threat to
> the Internet than the congestion-driven near-collapse of the NSF
> backbone in 1986.
It's not just bufferbloat: a number of network technologies are bunching
up packets and injecting them into the Internet with periodic bursts.
Unfortunately, I don't have good references to this; I gather this is
true of both wireless and wired technologies.
>
> This is a classic "black swan" situation in Nassim Taleb's sense; in
> today's Internet-dependent economy there is a potential for nearly
> inacalculable havoc in the worst case, but we don't even know in
> principle how to estimate the overall risk. Bufferbloat mitigation
> might keep us out of some very serious trouble, and is worth pursuing
> on those grounds alone.
It's actually a general fear of any periodic behaviour; I'm just spooked
to see it in such long period TCP traffic.
Van warned me about time based congestion phenomena in general.
next prev parent reply other threads:[~2011-02-07 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 14:39 Eric Raymond
2011-02-06 15:48 ` Jim Gettys
2011-02-06 20:20 ` Eric Raymond
2011-02-07 19:56 ` Jim Gettys [this message]
2011-02-08 6:54 ` [Bloat] Animation Richard Scheffenegger
2011-02-08 15:43 ` John W. Linville
2011-02-08 17:54 ` Eric Raymond
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=4D504E7F.6030602@freedesktop.org \
--to=jg@freedesktop.org \
--cc=bloat@lists.bufferbloat.net \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.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