General list for discussing Bufferbloat
 help / color / mirror / Atom feed
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: Sat, 05 Feb 2011 08:12:59 -0700	[thread overview]
Message-ID: <87vd0yikg4.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <4D4D53BA.5020003@freedesktop.org> (Jim Gettys's message of "Sat,  05 Feb 2011 08:42:18 -0500")

Jim Gettys <jg@freedesktop.org> writes:

> Several reactions:
> [elided]
> But memory is sooo cheap we've paved Texas over with extra road, just
> in case.

Why pick on Texas? The maximum latency yet reported was 40 seconds,
which is like 31 lunar distances (40/1.28), or half that if you are
measuring latency as RTT. 

It's one of those mind-bogglingly big numbers that douglas adams warned
us about. I wouldn't be surprised if someone reported RTT times as large
as between here and Venus.

Texas has enough problems.

> (QOS isn't universal, much less your complicated rules). Fix the
> bloat: then classify.

For years a very simple classification scheme has existed by
default. Most UDP packets actually used the TOS field sanely and the
 OS would prioritize those packets appropriately.

It worked, mostly. It's been devilish with SIP, however. 

A few other classification schemes have worked well in the field - the
wondershaper started a trend to prioritize interactive ack packets,
which helps interactive traffic (ssh, x11, stuff like that) a lot,
improving latency under load for latency dependent tcp streams.

Most of the others... Not so much. Interesting edge cases. Maybe a
diamond in the rough here and there.

Lastly, I make a distinction between QoS and AQM - one that's kind of
hard to define. To me AQM is about trying to ensure overall fairness and
goodput (techniques like RED and SFB) by managing queues sanely, and QoS
is about providing high speed lanes with special properties for certain
kinds of traffic.

Both ARE useful, but can be addressed in order of reducing unmanaged
buffers, applying AQM, and then QoS. 

> Many people will need to replace their routers, and will believe that
> is expensive; and to them, buying a $100 router *is*
> expensive. Remember your audience. And various ISP's aren't going to
> like the bottom line cost of replacing/upgrading all the broken
> equipment.

A lot of them can just get new firmware. Although it's likely that
dd-wrt and openwrt are worse, out of the box, at present.

My concern is after observing several reviews of new wireless kit in the
press that the most modern gear is exhibiting bufferbloat problems, as
yet undiagnosed. 

Possibly here:

http://online.wsj.com/article/SB10001424052748704774604576035691589888786.html

Certainly here:

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=416640&sid=635145ce6d7ee3bb695b39ace6b9c101


-- 
Dave Taht
http://nex-6.taht.net

  reply	other threads:[~2011-02-05 15:13 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 [this message]
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
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=87vd0yikg4.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