Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Adrian Popescu <adriannnpopescu@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake3 - source code and some questions
Date: Sun, 12 Apr 2015 15:33:31 +0300	[thread overview]
Message-ID: <CAF3M4P3THdGbBK6S-3AhOZ+F6ZRxo+Fj=WH7sa+WVwHg2wj+_A@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE1r9Qui4h0EZLEWOKDj9cjskE-7eX47V=1aR+hFEFFmRA@mail.gmail.com>

Thank you, Jonathan. High bandwidth home networks are becoming more
and more common. FTTH has very low latency of 1-2ms. fq_codel has
exhibited some weird behaviour, but I can't put my finger on it
because CPU usage wasn't a problem. Figuring out what's going on at
the kernel or fq_codel level can be complicated.

These high bandwidth connections with low latency are somewhat similar
to data centre networks. Some who co-locate their servers have 100mbps
of symmetric bandwidth outside of their network and they have 1 gbps
or 10 gbps within their network.

Setting up fq_codel properly can be difficult because the quantum, the
target and the interval need to be adjusted on high bandwidth & low
latency links. Figuring out if the changes have helped or hurt is
difficult because the network conditions can be different.

I can't wait to test cake3.


Regards,
Adrian


On Sun, Apr 12, 2015 at 1:24 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>> Can cake3 be used in a hierarchical setup, like htb?
>
> This is a trickier question. Cake is designed to be as simple to configure
> as possible, and a classful setup would work against that (it would
> instantly triple the number of tc invocations required). However, it could
> be used as a leaf qdisc with a separate classifier, if you really wanted to.
> I have trouble imagining why, though.
>
> To put it simply, we want to build the functionality for the most common use
> cases into cake natively, especially when they don't do any harm to be left
> switched on (by default) when not strictly needed.
>
> - Jonathan Morton

  reply	other threads:[~2015-04-12 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12  9:39 Adrian Popescu
2015-04-12  9:58 ` Jonathan Morton
2015-04-12 10:24 ` Jonathan Morton
2015-04-12 12:33   ` Adrian Popescu [this message]
2015-04-12 18:57     ` Jonathan Morton
2015-04-16 12:14       ` Adrian Popescu
2015-04-16 13:25         ` Jonathan Morton
2015-04-16 13:48           ` Adrian Popescu
2015-04-16 19:26             ` Dave Taht
2015-04-22 21:02               ` Adrian Popescu
2015-04-23  0:45                 ` Stephen Hemminger
2015-04-23  9:01                 ` Toke Høiland-Jørgensen
2015-04-23 10:56                   ` Adrian Popescu
2015-04-23 11:01                     ` Toke Høiland-Jørgensen
2015-04-23 11:05                       ` Adrian Popescu
2015-04-23 11:09                         ` Toke Høiland-Jørgensen
2015-04-23 11:13                           ` Jonathan Morton
2015-04-16 13:49           ` Sebastian Moeller

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='CAF3M4P3THdGbBK6S-3AhOZ+F6ZRxo+Fj=WH7sa+WVwHg2wj+_A@mail.gmail.com' \
    --to=adriannnpopescu@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