From: Thomas Renninger <trenn@suse.de>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Martin.Leisner@xerox.com, cpufreq@lists.linux.org.uk
Subject: Re: Overall picture of cpufreq..
Date: Mon, 14 Jan 2008 10:51:50 +0100 [thread overview]
Message-ID: <1200304310.23376.311.camel@queen.suse.de> (raw)
In-Reply-To: <478B0A82.6050503@wpkg.org>
On Mon, 2008-01-14 at 08:08 +0100, Tomasz Chmielewski wrote:
> Saru Addep schrieb:
> > Hi Thomas,
> >
> > So that means if we have an ondemand governor properly instrumented, there
> > is no need to have userspace governor. In the case of ondemand governor, the
> > only work that will be left to userspace would be to set the min, and max
> > freq. The complete intelligence of DVFS algoritm is present inside the
> > ondemand governor. Is my understanding correct.
Yes, this is correct.
> It looks to me that ondemand governor doesn't have "the complete
> intelligence".
>
> For example, it doesn't detect CPU load coming from some kernel tasks,
> like kcryptd: reads/writes from a device crypted with dm-crypt will be
> very slow if one uses the ondemand governor, as CPU speed will always be
> set to the lowest possible (so there is not enough power to
> crypt/decrypt data).
>
> Ironically, this is the only case when starting bzip2 will speed up your
> disk access... Or, use a userspace governor.
>
>
> See also http://bugzilla.kernel.org/show_bug.cgi?id=9729
I don't know about this one.
AFAIK there has been some work done there, I expect the bug in the
crypto area, not in cpufreq/ondemand layer.
A Xeon processor stepped down from 2800 to 350 looks bogus (maybe the
new ones even can, not sure), could it be that you are using
p4-clockmode driver which is doing throttling, not frequency scaling,
better try with acpi-cpufreq then.
Thomas
next prev parent reply other threads:[~2008-01-14 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 22:15 Overall picture of cpufreq Saru Addep
2008-01-11 22:50 ` Leisner, Martin
2008-01-13 22:54 ` Thomas Renninger
2008-01-14 2:12 ` Saru Addep
2008-01-14 7:08 ` Tomasz Chmielewski
2008-01-14 7:51 ` Saru Addep
2008-01-14 9:51 ` Thomas Renninger [this message]
2008-01-14 10:16 ` Tomasz Chmielewski
2008-01-14 10:32 ` Thomas Renninger
2008-01-14 10:59 ` Tomasz Chmielewski
2008-01-14 19:13 ` Saru Addep
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=1200304310.23376.311.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=Martin.Leisner@xerox.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=mangoo@wpkg.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