From: Benjamin Cronce <bcronce@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake vs fq_codel
Date: Fri, 20 Nov 2015 20:37:30 -0600 [thread overview]
Message-ID: <CAJ_ENFHAaVA=To_ZSqCTru4CdgDQxsLALdf0wUaWeXs5KVhbcg@mail.gmail.com> (raw)
In-Reply-To: <5C183BAB-3524-4A5B-98EC-E3A91267C44F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
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 <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 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
>
[-- Attachment #2: Type: text/html, Size: 1547 bytes --]
prev parent reply other threads:[~2015-11-21 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:17 Dave Taht
2015-11-19 23:33 ` Jonathan Morton
2015-11-21 2:37 ` Benjamin Cronce [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ_ENFHAaVA=To_ZSqCTru4CdgDQxsLALdf0wUaWeXs5KVhbcg@mail.gmail.com' \
--to=bcronce@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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