From: Simon Barber <simon@superduper.net>
To: "Roger Jørgensen" <rogerj@gmail.com>
Cc: codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] The challenge
Date: Wed, 09 May 2012 13:02:16 -0700 [thread overview]
Message-ID: <4FAACD48.9040100@superduper.net> (raw)
In-Reply-To: <CAKFn1SHdQyXMcaGgksA98HSgRymHC4Vp0wx-DiLwatShdUDmAg@mail.gmail.com>
significant queues only form where there is a bottleneck, so there
should not be long cascades of codel actually dropping.
Simon
On 05/09/2012 12:10 PM, Roger Jørgensen wrote:
> On Wed, May 9, 2012 at 7:16 AM, Simon Barber<simon@superduper.net> wrote:
>> One question now remains - will codel AQM be sufficient on it's own in
>> getting delays down to levels that users are happy with for the common
>> latency sensitive interactive traffic - VoIP, gaming and Skype for example -
>> or are the further reductions that can be had with traffic classification
>> and smart queuing algorithms necessary? The nicest part about codel on it's
>> own is that it works on opaque packets - it will handle VPNs and traffic
>> within them nicely. It gets away from all the complexity required to
>> classify traffic in a world where traffic is often trying to hide.
>
> I'm more worried about how long cascades of codel code in equipment
> will work together, add lots of traffic to the mix, just how will it
> behave then?
>
>
>
next prev parent reply other threads:[~2012-05-09 20:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 1:04 [Codel] " Dave Taht
2012-05-09 2:02 ` [Codel] [Bloat] " Kevin Gross
2012-05-09 3:13 ` [Codel] " Kathleen Nichols
2012-05-09 3:56 ` Dave Taht
2012-05-09 5:16 ` [Codel] [Bloat] " Simon Barber
2012-05-09 5:40 ` Eric Dumazet
2012-05-09 5:41 ` Dave Taht
2012-05-09 7:32 ` [Codel] [codel] some numbers on dual 10Gb links Eric Dumazet
2012-05-09 13:04 ` [Codel] [Bloat] The challenge Kevin Gross
2012-05-16 5:55 ` Jonathan Morton
2012-05-16 6:09 ` Eric Dumazet
2012-05-16 7:05 ` [Codel] Exploring the potential of codel, fq_codel, and qfq dave taht
2012-05-16 7:20 ` Dave Taht
2012-05-16 7:42 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 7:46 ` Eric Dumazet
2012-05-16 8:17 ` Eric Dumazet
2012-05-16 9:02 ` Jonathan Morton
2012-05-16 9:14 ` Eric Dumazet
2012-05-16 9:31 ` Jonathan Morton
2012-05-16 9:37 ` Eric Dumazet
2012-05-16 9:59 ` Jonathan Morton
2012-05-16 10:10 ` Eric Dumazet
2012-05-16 13:58 ` Eric Dumazet
2012-05-16 17:40 ` Rick Jones
2012-05-16 17:53 ` Eric Dumazet
2012-05-16 17:33 ` [Codel] " Rick Jones
2012-05-16 17:48 ` [Codel] [Bloat] " Eric Dumazet
2012-05-16 6:09 ` [Codel] [Bloat] The challenge Dave Taht
2012-05-16 6:31 ` Eric Dumazet
2012-05-16 8:15 ` Jonathan Morton
2012-05-09 19:10 ` Roger Jørgensen
2012-05-09 19:15 ` Dave Taht
2012-05-09 19:28 ` Dave Taht
2012-05-09 20:02 ` Simon Barber [this message]
2012-05-09 20:06 ` Fred Baker
2012-05-09 21:47 ` Jim Gettys
2012-05-09 23:58 ` Eric Dumazet
2012-05-10 2:34 ` Jonathan Morton
2012-05-10 2:37 ` Dave Taht
2012-05-10 6:35 ` David Woodhouse
2012-05-10 6:54 ` Jonathan Morton
2012-05-10 7:02 ` David Woodhouse
2012-05-10 14:25 ` Justin McCann
2012-05-10 14:42 ` David Woodhouse
2012-05-10 15:34 ` Neil Davies
2012-05-10 21:20 ` Jim Gettys
2012-05-14 7:27 ` Jonathan Morton
2012-05-14 7:34 ` Eric Dumazet
2012-05-14 13:55 ` David Woodhouse
2012-05-18 20:56 ` [Codel] [Bloat] Linux-able modems Jonathan Morton
2012-05-18 21:36 ` Dave Taht
2012-05-18 22:34 ` 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FAACD48.9040100@superduper.net \
--to=simon@superduper.net \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=rogerj@gmail.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