From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Piero <ottuzzi@gmail.com>
Cc: linux-amlogic@lists.infradead.org
Subject: Re: Odroidc1 DVFS
Date: Sun, 17 Feb 2019 15:13:40 +0100 [thread overview]
Message-ID: <CAFBinCC5YORZB2X7ypHZHaxqjkkwAcOxmpWG05KEq_Q6Y0Lc3A@mail.gmail.com> (raw)
In-Reply-To: <CAPo5REFbUZ6fTZUAPJPqCnBK2Yt7BcCUfFm0GAhZWROf5Oe8yA@mail.gmail.com>
Hi Piero,
On Tue, Feb 12, 2019 at 11:27 AM Piero <ottuzzi@gmail.com> wrote:
>
> Hi Martin,
>
> I recompiled integ branch with CONFIG_PWM_MESON=y and now DVFS is
> working as expected.
great - thank you for the feedback! :)
> I did some tests using sbc-bench:
>
> * Original Odroid Ubuntu 16.04 with 3.10 kernel (1824MHz): http://ix.io/1zdB
> * Armbian 5.75 with 5.0.0-rc5 kernel (1536MHz DVFS): http://ix.io/1APH
>
> Original 3.10 kernel has a big big margin on tinymembench (about twice
> as fast as 5.0.0-rc5 with DVFS); 3.10 is 50% faster in OpenSSL and
> both kernels are tie on 7-zip (a bit faster 5.0.0-rc5). Do you have
> any idea on how to explain the difference in tinymembench? I do not
> think 300MHz overclocking is enough to explain the difference.
Did you compare kernel 3.10 with 5.0.0-rc on other hardware as well?
I have no idea why it there's such a huge difference between these two
kernel versions (in some of your tests). The only thing that came to
my mind is all the hardening for the "spectre" vulnerabilities, but I
can't tell if for example tinymembench really suffers from that.
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-02-17 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 14:52 Odroidc1 DVFS Piero
2019-02-08 19:44 ` Martin Blumenstingl
2019-02-12 10:27 ` Piero
2019-02-17 14:13 ` Martin Blumenstingl [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFBinCC5YORZB2X7ypHZHaxqjkkwAcOxmpWG05KEq_Q6Y0Lc3A@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=ottuzzi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.