From: Jim Gettys <jg@freedesktop.org>
To: Rick Jones <rick.jones2@hpe.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Difference between codel and fq_codel?
Date: Fri, 8 Apr 2016 15:37:34 -0400 [thread overview]
Message-ID: <CAGhGL2C7f8Q3nJb9hBYgwJ-iR9RQU5Jqb+uDAM2xa_875M_mGA@mail.gmail.com> (raw)
In-Reply-To: <56B25E76.3080506@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On Wed, Feb 3, 2016 at 3:09 PM, Rick Jones <rick.jones2@hpe.com> wrote:
> On 02/03/2016 11:22 AM, John Klimek wrote:
>
>> I'm currently using pfaense which only supports codel and not
>> fq_codel. Is there a big difference between them? Is it worth
>> looking into using a different router?
>>
>
> My simplistic understanding is fq_codel creates several/many different
> queues, spreading flows across those queues and applying codel on each
> queue.
>
>
> http://man7.org/linux/man-pages/man8/tc-fq_codel.8.html
>
> http://man7.org/linux/man-pages/man8/tc-codel.8.html
It also preferentially schedules "new" queues, relative to queues that
have a standing queue. So short transactions such as dchp, ra, short RPC
transactions, VOIP, etc fly through the router relative to bulk TCP flows.
This algorithm does really wonderful things for any flow that is a "good
citizen" by pacing their traffic at their share of available bandwidth,
rather than bursting their traffic. For the first time, there is incentive
to be a "good citizen" in your behavior.
>
>
> rick jones
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2647 bytes --]
next prev parent reply other threads:[~2016-04-08 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 19:22 John Klimek
2016-02-03 20:09 ` Rick Jones
2016-04-08 19:36 ` Jonathan Morton
2016-04-08 19:37 ` Jim Gettys [this message]
2016-02-03 20:33 ` Toke Høiland-Jørgensen
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGhGL2C7f8Q3nJb9hBYgwJ-iR9RQU5Jqb+uDAM2xa_875M_mGA@mail.gmail.com \
--to=jg@freedesktop.org \
--cc=bloat@lists.bufferbloat.net \
--cc=rick.jones2@hpe.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