Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: dpreed@reed.com
Cc: Kathleen Nichols <nichols@pollere.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] fq_codel is two years old
Date: Fri, 16 May 2014 10:52:59 -0400	[thread overview]
Message-ID: <15152.1400251979@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 15 May 2014 16:32:55 -0400." <1400185975.95298344@apps.rackspace.com>

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

On Thu, 15 May 2014 16:32:55 -0400, dpreed@reed.com said:

> And in the end of the day, the problem is congestion, which is very
> non-linear.  There is almost no congestion at almost all places in the Internet
> at any particular time.  You can't fix congestion locally - you have to slow
> down the sources across all of the edge of the Internet, quickly.

There's a second very important point that somebody mentioned on the NANOG
list a while ago:

If the local router/net/link/whatever isn't congested, QoS cannot do anything
to improve life for anybody.

If there *is* congestion, QoS can only improve your service to the normal
uncongested state - and it can *only do so by making somebody else's experience
suck more*....


[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2014-05-16 14:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ACF89699-67A0-4853-843F-CAC9BDE97CCB@gmail.com>
2014-05-14 21:01 ` [Cerowrt-devel] " Rich Brown
2014-05-14 22:32   ` [Cerowrt-devel] [Bloat] " Kathleen Nichols
2014-05-15  1:25     ` Dave Taht
2014-05-15 13:47       ` dpreed
2014-05-15 16:32         ` Kathleen Nichols
2014-05-15 20:32           ` dpreed
2014-05-15 22:53             ` Jonathan Morton
2014-05-16  9:38               ` Michael Welzl
2014-05-16 14:52             ` Valdis.Kletnieks [this message]
2014-05-16 16:06               ` Jim Gettys
2014-05-16 20:17                 ` dpreed
2014-05-15 23:46         ` David Lang
2014-05-16  1:01           ` dpreed
2014-05-16  1:13             ` Dave Taht
2014-05-16  1:15             ` David Lang
2014-05-16  3:16               ` David P. Reed
2014-05-16  3:23                 ` David Lang
2014-05-16 12:33                   ` David P. Reed
2014-05-16 14:21                   ` David P. Reed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15152.1400251979@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=nichols@pollere.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