From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: [Cake] Test results
Date: Tue, 24 Nov 2015 12:02:39 +0100 [thread overview]
Message-ID: <CAA93jw7Bcg_4CotL0ZRVtuBgNadkWj0-3wLwOkOgV1vwjCvBdg@mail.gmail.com> (raw)
up until a few moments ago I had assumed that cake was peeling...
and I was composing an email talking about how all cake's optimizations
seemed not to be any better, and in some cases, worse, than sqm-scripts
in all the test series with offloads on I ran last week. Now I know....
I was prepping to rip out a lot of the stuff that we have not tested at
scale - like the invsqrt cache, most of the other mods to codel, and then
take a hard look at the target and quantum calculations.
one thing I think would be helpful to everyone is to start publishing
test results, as well as perf results for arm, mips, and x86_64.
But I am not sure what people would find useful.
reply other threads:[~2015-11-24 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw7Bcg_4CotL0ZRVtuBgNadkWj0-3wLwOkOgV1vwjCvBdg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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