General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: richard <richard@pacdat.net>
To: esr@thyrsus.com
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] First draft of complete "Bufferbloat And You" enclosed.
Date: Tue, 08 Feb 2011 10:31:56 -0800	[thread overview]
Message-ID: <1297189916.26293.29.camel@amd.pacdat.net> (raw)
In-Reply-To: <20110208181811.GD7744@thyrsus.com>

On Tue, 2011-02-08 at 13:18 -0500, Eric Raymond wrote:
> Justin McCann <jneilm@gmail.com>:
> > This may be intentional, but the text launches into an explanation of
> > why bufferbloat is bad without concisely explaining what it is--- you
> > have to read the whole first two sections before it's very clear.
> 
> Not intentional, exactly, but's inherent.  Thec reader *can't* get what
> bufferbloat.
> 
> > The second of the three main tactics states, "Second, we can decrease
> > buffer sizes.  This cuts the delay due to latency and decreases the
> > clumping effect on the traffic." Latency *is* delay; perhaps "cuts the
> > delay due to buffering" or "due to queueing" would be better, if more
> > tech-ese.
> 
> Good catch, I'll fix.
>  
> > I've re-read through the Bell Labs talk, and some of the earlier
> > posts, but could someone explain the "clumping" effect? I understand
> > the wild variations in congestion windows ("swing[ing] rapidly and
> > crazily between emptiness and overload"), but clumping makes me think
> > of closely spaced packet intervals.
> 
> It's intended to.  This is what I got from jg's talk, and I wrote the
> SOQU scenario to illustrate it. If my understanding is incorrect (and
> I see that you are saying it is) one of the real networking people
> here needs to whack me with the enlightenment stick.
> 
> The underlying image in my just-so stories about roads and parking lots
> is that packet flow coming in smooth on the upstream side of a buffwer
> gets turned into a buffer fill, followed by a burst of packets as it 
> overflows, followed by more data coming into the buffer, followed by
> overflow...repeat.

My electronics (analog, tube, etc.) background makes me view a lot of
this as "tuned" circuits - capacitors, resistors, coils, etc.

If I read things correctly, there are a number of different ways buffers
are used/abused. They're all FIFO (I hope - somebody disabuse me of this
idea if they have evidence) but how they deal with high/low water marks
seems to make a difference.

Actual processor capabilities (and overall system load) may also play a
role - the embedded stack processor and/or the system's CPU including
things like interrupt load, bus mastering, DMA, etc.

If the interface is capable of full bandwidth in and out at the same
time, and high/low water mark detection is quick, then I'd think this is
a circuit that has little tendency to oscillate at any low, detectable
frequency.

If the interface is not capable of full bandwidth in and out at the same
time, and/or the detection of or settings for high/low water mark in the
buffer are screwy, then the system will oscillate at a low frequency and
you'll get clumping.

I'd expect to see this on cheap Gbit Ethernet cards on PCI bus (lots of
interrupts to the main CPU) as the system's load rises for example; one
of the reasons I've stopped using them, even on lightly loaded links.

richard

-- 
Richard C. Pitt                 Pacific Data Capture
rcpitt@pacdat.net               604-644-9265
http://digital-rag.com          www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333  57F0 4F18 AF98 9F59 DD73


  reply	other threads:[~2011-02-08 18:32 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 [this message]
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
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=1297189916.26293.29.camel@amd.pacdat.net \
    --to=richard@pacdat.net \
    --cc=bloat@lists.bufferbloat.net \
    --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