From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 6EF5B21F2F1 for ; Fri, 20 Nov 2015 18:37:31 -0800 (PST) Received: by ykba77 with SMTP id a77so185692520ykb.2 for ; Fri, 20 Nov 2015 18:37:30 -0800 (PST) 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=Q8SWuph3A4QrGrKp3IB9SpQwsd8x8Xocwyx6790iiu0=; b=uj83jb9Xw5AEFQdp8ZatNHksZXAwJb9MfZ7V/vC6WPD2OXnTyRb1Vr4twmz9xhBWFA 7Iz2QNLHrF23OJo9+xqoPpmVwTa+oCFH9vHyJFnNFo6uuuaz4uVIG3g6Ga9ZYIYrQwo4 OQsrEU27k1NP6ZzhiKiVO6GuQTqmSkRVRndRmW3O14ckeBDbkNfvzYjacvN6yxAmP1uv AihwUslqpZ/FcRxv40bhSyM73sdoHU8RRSEDY979WfMNG+VnkWXzIi/1zzErKCVrwQVe jj1E68cc2YlhuxG5jWH1UXn7sfqJuvzK+tr5MEM0h2JS91GB68mgUDeCYbilIhop/vda sHFQ== MIME-Version: 1.0 X-Received: by 10.129.55.76 with SMTP id e73mr12817639ywa.162.1448073450842; Fri, 20 Nov 2015 18:37:30 -0800 (PST) Received: by 10.13.236.148 with HTTP; Fri, 20 Nov 2015 18:37:30 -0800 (PST) In-Reply-To: <5C183BAB-3524-4A5B-98EC-E3A91267C44F@gmail.com> References: <5C183BAB-3524-4A5B-98EC-E3A91267C44F@gmail.com> Date: Fri, 20 Nov 2015 20:37:30 -0600 Message-ID: From: Benjamin Cronce To: Jonathan Morton Content-Type: multipart/alternative; boundary=001a1144002ca5717e052503df9a Cc: cake@lists.bufferbloat.net Subject: Re: [Cake] cake vs fq_codel X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 02:37:54 -0000 --001a1144002ca5717e052503df9a Content-Type: text/plain; charset=UTF-8 fq_Codel is still useful if you need a traffic shaper with bandwidth controls, like HFS. Maybe fq_Codel could be updated with "ways" like Cake, to remove hash collisions. On Thu, Nov 19, 2015 at 5:33 PM, Jonathan Morton wrote: > > > On 19 Nov, 2015, at 11:17, Dave Taht wrote: > > > > A) Under what circumstances is cake a replacement for fq_codel? > > When shaping or Diffserv prioritisation is required, or when flow hash > collisions are likely to be problematic. > > > B) When is fq_codel a better choice than cake? > > When none of the above apply, and a slight improvement in CPU and memory > overhead is desirable. > > - Jonathan Morton > > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake > --001a1144002ca5717e052503df9a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
fq_Codel is still useful if you need a traffic shaper with= bandwidth controls, like HFS. Maybe fq_Codel could be updated with "w= ays" like Cake, to remove hash collisions.

On Thu, Nov 19, 2015 at 5:33 PM, Jonath= an Morton <chromatix99@gmail.com> wrote:

> On 19 Nov, 2015, at 11:17, Dave Taht <dave.taht@gmail.com> wrote:
>
> A) Under what circumstances is cake a replacement for fq_codel?

When shaping or Diffserv prioritisation is required, or when flow ha= sh collisions are likely to be problematic.

> B) When is fq_codel a better choice than cake?

When none of the above apply, and a slight improvement in CPU and me= mory overhead is desirable.

=C2=A0- Jonathan Morton

_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake

--001a1144002ca5717e052503df9a--