From: Dave Jones <davej@codemonkey.org.uk>
To: Scott James Remnant <scott@canonical.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Change link order of x86 cpufreq modules
Date: Fri, 20 Feb 2009 12:41:48 -0500 [thread overview]
Message-ID: <20090220174148.GB9995@codemonkey.org.uk> (raw)
In-Reply-To: <1235151575.6467.68.camel@quest>
On Fri, Feb 20, 2009 at 05:39:35PM +0000, Scott James Remnant wrote:
> On Fri, 2009-02-20 at 17:36 +0000, Matthew Garrett wrote:
>
> > On Fri, Feb 20, 2009 at 05:29:52PM +0000, Scott James Remnant wrote:
> >
> > > In fact, we've noticed severe regressions with p4-clockmod over simply
> > > having no scaling driver at all - and are not going to built it into our
> > > kernels.
> >
> > It makes sense to have p4-clockmod from a thermal management
> > perspective. We should probably bump its transition latency to more than
> > 10ms to prevent ondemand binding to it.
> >
> If that's possible; that'd be good.
>
> The trouble with it is that it never seems to bring the CPU anywhere
> near maximum performance.
This is one reason why in .30 the user interface for p4-clockmod is disabled.
It'll only get throttled when ACPI goes into OMG I'M OVERHEATING mode,
and ramp back up once it cools off.
p4-clockmod and ondemand is a recipe for fail.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2009-02-20 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 18:28 [PATCH] cpufreq: Change link order of x86 cpufreq modules Matthew Garrett
2009-02-18 18:31 ` Ingo Molnar
2009-02-18 18:34 ` Dave Jones
2009-02-18 18:36 ` Matthew Garrett
2009-02-18 19:09 ` Ingo Molnar
2009-02-19 11:54 ` Alan Jenkins
2009-02-19 12:03 ` Ingo Molnar
2009-02-23 21:12 ` Thomas Renninger
2009-02-23 21:47 ` Kay Sievers
2009-02-20 17:29 ` Scott James Remnant
2009-02-20 17:36 ` Matthew Garrett
2009-02-20 17:39 ` Scott James Remnant
2009-02-20 17:41 ` Dave Jones [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=20090220174148.GB9995@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=scott@canonical.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.