From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 550DE208AC5; Tue, 8 May 2012 22:41:56 -0700 (PDT) Received: by wibhn19 with SMTP id hn19so43002wib.10 for ; Tue, 08 May 2012 22:41:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O88RTz1aB0Hdj0ghJsoz+oK5V/jH2ZrASdGkIwPL0oU=; b=Y/J8vRswHYmhRUJIkVY9hJQy7CO2hZdgG5QqTwYpKFHRX1NkSbXSObNE8iFECabeNb EtCFVJiBAPlvggj2VxxRSXEKbl/Vv198yDKeRyqcUcIrKtCJVKJBIlGtgGFfp5yqYCs4 8CXdc4FI85O4djGoXZimGzdd13qRKUxYuG4Red1up0RRIFRGNospqWz6+KagIeKPEpU8 zmuf4V/X/61IpggNc1Yt5xdWMVkd8RtvRA9hEfiMhji6esU/KkqIhlhZmhKcBh+e0po/ Tkixol7K8+qvJ3wk42n1kKOO0PUlKF1DnX/a21NADKYnxlt60hdd52IcAGurzlGCSO2k Rocg== MIME-Version: 1.0 Received: by 10.180.20.137 with SMTP id n9mr3019997wie.3.1336542114357; Tue, 08 May 2012 22:41:54 -0700 (PDT) Received: by 10.223.112.66 with HTTP; Tue, 8 May 2012 22:41:54 -0700 (PDT) In-Reply-To: <1336542018.3752.3235.camel@edumazet-glaptop> References: <4FA9FDC0.9010600@superduper.net> <1336542018.3752.3235.camel@edumazet-glaptop> Date: Tue, 8 May 2012 22:41:54 -0700 Message-ID: From: Dave Taht To: Eric Dumazet Content-Type: multipart/alternative; boundary=bcaec53d5ce5f41f9c04bf93f568 Cc: codel@lists.bufferbloat.net, bloat Subject: Re: [Codel] [Bloat] The challenge X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2012 05:41:56 -0000 --bcaec53d5ce5f41f9c04bf93f568 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, May 8, 2012 at 10:40 PM, Eric Dumazet wrote= : > On Tue, 2012-05-08 at 22:16 -0700, Simon Barber 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. > > It all depends on the requirements you have. > > To me, CoDel is a RED replacement, because it provides something easier > to deploy (no knobs). So it wont solve by itself cases where you want > something that could not be done by a single RED queue. > > I like to see Codel as a basic unit, to replace RED (or pfifo if some > fools still use this for whatever reasons) in a tree involving > classifiers and FQ. > > +10 --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net --bcaec53d5ce5f41f9c04bf93f568 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, May 8, 2012 at 10:40 PM, Eric Du= mazet <eric.dumazet@gmail.com> wrote:
On Tue, 2012-05-08 at 22:16 -0700, Simon Barber wrote: > One question now remains - will codel AQM be sufficient on it's ow= n 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 wi= ll
> handle VPNs and traffic within them nicely. It gets away from all the<= br> > complexity required to classify traffic in a world where traffic is > often trying to hide.

It all depends on the requirements you have.

To me, CoDel is a RED replacement, because it provides something easier
to deploy (no knobs). So it wont solve by itself cases where you want
something that could not be done by a single RED queue.

I like to see Codel as a basic unit, to replace RED (or pfifo if some
fools still use this for whatever reasons) in a tree involving
classifiers and FQ.


+10



-- =
Dave T=E4ht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
--bcaec53d5ce5f41f9c04bf93f568--