From: Andrew Morton <akpm@linux-foundation.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date: Sun, 3 Feb 2008 16:32:55 -0800 [thread overview]
Message-ID: <20080203163255.467256d4.akpm@linux-foundation.org> (raw)
In-Reply-To: <200801261506.28544.toralf.foerster@gmx.de>
On Sat, 26 Jan 2008 15:06:25 +0100 Toralf Förster <toralf.foerster@gmx.de> wrote:
> I use a 1-liner for a simple performance check : "time factor 819734028463158891"
> Here is the result for the new (Gentoo) kernel 2.6.24:
>
> With the ondemand governor of the I get:
>
> tfoerste@n22 ~/tmp $ time factor 819734028463158891
> 819734028463158891: 3 273244676154386297
>
> real 0m32.997s
> user 0m15.732s
> sys 0m0.014s
>
> With the ondemand governor the CPU runs at 600 MHz,
> whereas with the performance governor I get :
>
> tfoerste@n22 ~/tmp $ time factor 819734028463158891
> 819734028463158891: 3 273244676154386297
>
> real 0m10.893s
> user 0m5.444s
> sys 0m0.000s
>
> (~5.5 sec as I expected) b/c the CPU is set to 1.7 GHz.
>
> The ondeman governor of previous kernel versions however automatically increased
> the CPU speed from 600 MHz to 1.7 GHz.
>
> My system is a ThinkPad T41, I'll attach the .config
>
Let's cc the cpufreq list.
If nothing happens (often the case), please raise a report at
bugzilla.kernel.org so we can track the presence of the regression.
Thanks.
next prev parent reply other threads:[~2008-02-04 0:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 14:06 (ondemand) CPU governor regression between 2.6.23 and 2.6.24 Toralf Förster
2008-02-04 0:32 ` Andrew Morton [this message]
2008-02-04 0:36 ` Andrew Morton
2008-02-04 17:44 ` Pallipadi, Venkatesh
2008-02-04 19:18 ` Toralf Förster
-- strict thread matches above, loose matches on Subject: below --
2008-01-26 17:11 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster
2008-01-27 14:46 ` Srivatsa Vaddagiri
2008-01-27 15:06 ` Toralf Förster
2008-01-27 16:54 ` Srivatsa Vaddagiri
2008-01-27 16:57 ` Toralf Förster
2008-01-27 21:27 ` Peter Zijlstra
2008-01-27 22:32 ` Ingo Molnar
2008-01-28 8:38 ` Helge Hafting
2008-01-26 21:38 ` Toralf Förster
2008-01-26 21:45 ` Sam Ravnborg
[not found] ` <200801271200.04971.toralf.foerster@gmx.de>
[not found] ` <1201433167.22060.10.camel@homer.simson.net>
2008-01-27 12:39 ` Toralf Förster
2008-01-27 18:58 ` Mike Galbraith
2008-01-27 21:14 ` Toralf Förster
2008-01-27 21:25 ` Peter Zijlstra
2008-01-28 13:18 ` Ingo Molnar
2008-01-28 15:16 ` Toralf Förster
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=20080203163255.467256d4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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