Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@reed.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Ubiquiti QOS
Date: Mon, 26 May 2014 08:31:12 -0700	[thread overview]
Message-ID: <b5c8b68c-b985-480d-baca-6555cd629f0b@katmail.1gravity.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1405261604541.29282@uplift.swm.pp.se>

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

Codel and PIE are excellent first steps... but I don't think they are the best eventual approach.  I want to see them deployed ASAP in CMTS' s and server load balancing networks... it would be a disaster to not deploy the far better option we have today immediately at the point of most leverage. The best is the enemy of the good.

But, the community needs to learn once and for all that throughput and latency do not trade off. We can in principle get far better latency while maintaining high throughput.... and we need to start thinking about that.  That means that the framing of the issue as AQM is counterproductive. 

On May 26, 2014, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>On Mon, 26 May 2014, dpreed@reed.com wrote:
>
>> I would look to queue minimization rather than "queue management"
>(which 
>> implied queues are often long) as a goal, and think harder about the 
>> end-to-end problem of minimizing total end-to-end queueing delay
>while 
>> maximizing throughput.
>
>As far as I can tell, this is exactly what CODEL and PIE tries to do.
>They 
>try to find a decent tradeoff between having queues to make sure the
>pipe 
>is filled, and not making these queues big enough to seriously affect 
>interactive performance.
>
>The latter part looks like what LEDBAT does?
><http://tools.ietf.org/html/rfc6817>
>
>Or are you thinking about something else?

-- Sent from my Android device with K-@ Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2044 bytes --]

  reply	other threads:[~2014-05-26 15:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  6:17 Dane Medic
2014-05-25 14:23 ` Valdis.Kletnieks
2014-05-25 15:42 ` Mikael Abrahamsson
2014-05-25 20:00   ` dpreed
2014-05-26  0:18     ` Mikael Abrahamsson
2014-05-26  4:49       ` dpreed
2014-05-26 13:02         ` Mikael Abrahamsson
2014-05-26 14:01           ` dpreed
2014-05-26 14:11             ` Mikael Abrahamsson
2014-05-26 15:31               ` David P. Reed [this message]
2014-05-27 21:19                 ` David Lang
2014-05-27 22:00                   ` Dave Taht
2014-05-27 23:27                     ` David Lang
2014-05-28  2:12                       ` Dave Taht
2014-05-28  3:21                         ` David Lang
2014-05-28 15:52                           ` dpreed
2014-05-28 16:34                             ` David Lang
2014-05-27 15:23     ` Jim Gettys
2014-05-27 17:31       ` Dave Taht
2014-05-28 15:33         ` dpreed
2014-05-28 15:20       ` dpreed
2014-05-28 18:33         ` David Lang
2014-05-29 12:11           ` David P. Reed
2014-05-29 15:29             ` dpreed
2014-05-29 19:30               ` David Lang
2014-05-29 23:40             ` Michael Richardson
2014-05-30  0:32               ` David P. Reed
2014-05-30  0:36               ` Dave Taht
2014-05-25 18:39 ` Sebastian Moeller
2014-05-25 19:33   ` Dave Taht

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=b5c8b68c-b985-480d-baca-6555cd629f0b@katmail.1gravity.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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