From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] 450 flow tests
Date: Wed, 22 Apr 2015 21:52:54 +0300 [thread overview]
Message-ID: <926B60D5-224C-498A-8790-B7C7B441B052@gmail.com> (raw)
In-Reply-To: <CAA93jw5_gJYLHHNr_nC+zzt3zApcG5KfouGvb8F_z+xrrNW6BQ@mail.gmail.com>
> On 22 Apr, 2015, at 18:59, Dave Taht <dave.taht@gmail.com> wrote:
>
> * Cake totally controls things
Yay! And there really aren’t very many collisions there, so the FQ logic is still mostly working as designed.
> * As does cake flowblind, but less so
That is surprising, actually. With shaping off, all packets having the same DSCP and with FQ disabled, it should behave similarly to ns4_codel (as I used codel4.h as a basis for codel5.h). That the three “way” stats counters remain at zero confirms that the FQ logic is being completely bypassed (since if the hash was fixed at zero and the FQ logic still ran, you’d see at least some misses and indirect hits as well as a lot of collisions, since the set-associative logic would still search the first 8 queues).
But I didn’t notice an ns4_codel test run in your post. A direct comparison might be apt, and then we can look at the differences between ns4_codel and the other codels in isolation.
- Jonathan Morton
next prev parent reply other threads:[~2015-04-22 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 15:59 Dave Taht
2015-04-22 18:52 ` Jonathan Morton [this message]
2015-04-23 2:08 ` Dave Taht
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=926B60D5-224C-498A-8790-B7C7B441B052@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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