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: Thu, 16 Apr 2015 15:14:10 +0300 [thread overview]
Message-ID: <CAF3M4P3o9UsJ8rmdvR24JYaEVUK-DhkOOZyqPJ29pkuO6i2TPA@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE3WRPX+ogKbwGR9qr6adi=3QFN6-2n9NjndNG45cLh8Tg@mail.gmail.com>
That answers my question. Will the changes to codel made by cake be
put into fq_codel?
On Sun, Apr 12, 2015 at 9:57 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> This is a question worth discussing. There is a certain amount of
> controversy over the actual meaning, utility and constraints of the target
> parameter, although the interval parameter is fairly well understood as a
> rough (order of magnitude) estimate of the prevailing RTT.
>
> Note that even with FTTP, while the RTT to the head end may be unusually
> low, the RTTs to interesting servers will still be in roughly the same range
> as on a good quality ADSL link. This is especially true if the interesting
> servers tend to be at the other end of the country/continent or on the other
> side of an ocean. This variability is within Codel's capacity.
>
> Due to the Diffserv and flow isolation features of cake, the latency
> minimization feature provided by Codel also isn't as critical to tune as it
> is when standalone, or with a lesser flow isolation system such as
> fq_codel's collision prone hash function. I think this is sufficient to make
> further tuning unnecessary up to 1 gigabit, whether on a LAN or over the
> internet, and since I haven't seen any home affordable gear for more than a
> gigabit yet - marketing tricks by Wi-Fi vendors aside - I don't think it's
> worth thinking too hard about pushing that higher in the home use case.
> Fq_codel also works quite well on a LAN already.
>
> The difference in a datacentre is that typical native RTTs are measured in
> microseconds, well outside the range that Codel is by default tuned for. The
> bandwidths involved also mean that the standard 5ms target invokes a large
> amount of buffered data. Additionally, we're inherently talking about a
> wholly local environment, so there is no need to adapt to internet scale
> RTTs.
>
> For those cases where you do have a datacentre like environment connected to
> an internet like environment, the solution is obvious. Deploy datacentre
> tuned AQM (which might be fq_codel with altered parameters) within the
> datacentre, and put cake at the gateway(s) to the internet. Job done.
>
> - Jonathan Morton
next prev parent reply other threads:[~2015-04-16 12:14 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
2015-04-12 18:57 ` Jonathan Morton
2015-04-16 12:14 ` Adrian Popescu [this message]
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=CAF3M4P3o9UsJ8rmdvR24JYaEVUK-DhkOOZyqPJ29pkuO6i2TPA@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