From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 36652] New: Ondemand governor is hyperactive
Date: Sat, 4 Jun 2011 16:50:05 GMT [thread overview]
Message-ID: <bug-36652-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=36652
Summary: Ondemand governor is hyperactive
Product: Power Management
Version: 2.5
Kernel Version: 2.6.39
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: timshel@rocketmail.com
Regression: No
According to some posts Ondemand governor should be the best even in battery
mode because the cpu can sleep longer if the tasks get finished sooner.
This is probably true but at the moment it isn't because Ondemand even scales
up if the cpu doesn't has anything to do.
This might have something to do that the governor can't anticipate how long or
how much this task will need so he scales up all the time if the cpu is used
but this is bad in battery mode.
So either there is a bug in Ondemand governor which should be fixed or if this
happens purely out of performance reasons there should be an additional mode
for battery where it only scales up if the cpu can't handle this with the
lowest task.
I know that there is the conservative governor but it is too slow, for example
it takes ages to scale down.
With powersave the battery time is increased significantly (at least 1W less)
and for most tasks the lowest frequency is fine.
I mean in this idle case of the screen shot it doesn't make any sense to scale
up all the time but even if you play a video there is no need for the highest
frequency and especially not the turbo mode.
I mean why are there more than two frequencies if only they get used?
I am using openSUSE 11.4 with Kernel 2.6.37. I had the same problem with
Vanilla 2.6.39.
My processor is a Core i5 of the first generation.
If you need any additional information let me know.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-06-04 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 16:50 bugzilla-daemon [this message]
2011-06-04 17:37 ` [Bug 36652] Ondemand governor is hyperactive bugzilla-daemon
2011-06-04 17:42 ` bugzilla-daemon
2011-06-04 17:44 ` bugzilla-daemon
2011-06-07 1:57 ` bugzilla-daemon
2011-06-10 7:47 ` bugzilla-daemon
2011-06-10 7:58 ` bugzilla-daemon
2012-01-18 5:18 ` bugzilla-daemon
2012-05-13 14:29 ` bugzilla-daemon
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=bug-36652-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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).