From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: mpartap@gmx.net, merlijn@wizzup.org,
kernel list <linux-kernel@vger.kernel.org>,
sre@kernel.org, nekit1000@gmail.com, linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: v4.18-rc1 on droid 4: very bad CPU performance
Date: Wed, 4 Jul 2018 22:12:18 +0200 [thread overview]
Message-ID: <20180704201218.GC13932@amd> (raw)
In-Reply-To: <20180628090655.GL112168@atomide.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1323 bytes --]
Hi!
> > I was about to add "facepalm" emoji here, as disabling l2 cache is
> > major mistake. OTOH if you also see 20 seconds, then either there is
> > another problem, or you need to enable l2 cache, too (and I don't have
> > to feel too bad for misconfiguring it).
>
> OK. I checked and duovero runs only at 600MHz. I can only
> get down to 19 seconds with omap2plus_defconfig if I disable
> CONFIG_CPU_FREQ so the max speed is maintained from bootloader.
> Otherwise it runs at most at 1GHz, I think any higher speeds
> need smartreflex and voltage scaling working which we don't
> have in the mainline kernel. Not sure what happens with higher
> speeds with mainline kernel or if they are unsafe in the long
> run.
>
> Anyways, care to post your .config somewhere so I can see what
> the numbers are for me with it?
I'm attaching config I'm using for v4.18. In current boot, bzip2 takes
16 seconds.
user@devuan:~$ time cat /dev/urandom | head -c 10000000 | sudo nice
-n -19 bzip2 -9 - | wc -c
10044705
15.68user 0.53system 15.93 (0m15.931s) elapsed 101.82%CPU
I guess I should go back to v4.17 to get 12 seconds..?!
Confused,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.1.2: config.gz --]
[-- Type: application/gzip, Size: 29025 bytes --]
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-07-04 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 12:15 v4.18-rc1 on droid 4: very bad CPU performance Pavel Machek
2018-06-22 7:20 ` Tony Lindgren
2018-06-22 7:49 ` Tony Lindgren
2018-06-25 9:49 ` Pavel Machek
2018-06-26 6:16 ` Tony Lindgren
2018-06-27 13:26 ` Pavel Machek
2018-06-27 19:48 ` Pavel Machek
2018-06-27 20:58 ` Pavel Machek
2018-06-28 9:06 ` Tony Lindgren
2018-07-04 20:12 ` Pavel Machek [this message]
2018-07-04 20:22 ` Pavel Machek
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=20180704201218.GC13932@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).