From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date: Sat, 26 Jan 2008 19:46:51 +0100 [thread overview]
Message-ID: <200801261946.54518.toralf.foerster@gmx.de> (raw)
In-Reply-To: <479B69D2.5050603@wpkg.org>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
The problem is the same as described here : http://lkml.org/lkml/2007/10/21/85
If I run dnetc even with lowest prority than the CPU stays at 600 MHz regardless
of any other load (eg. rsyncing, svn update, compiling, ...)
Stopping the dnetc process immediately speeds up the CPU up to 1.7 GHz.
Am Samstag, 26. Januar 2008 schrieben Sie:
> During the test, run top, and watch your CPU usage. Does it go above 80%
> (the default for
> /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold).
No, instead I get :
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7294 dnetc 39 19 664 348 264 R 49.5 0.0 0:48.68 dnetc
7310 tfoerste 20 0 1796 492 428 R 48.5 0.0 0:07.19 factor
7050 root 20 0 96736 8872 3972 S 0.7 0.9 0:02.99 X
> What CPUFreq processor driver are you using?
I use the native kernel built-in ondemand governor. BTW, here are the settings:
n22 /sys/devices/system/cpu/cpu0/cpufreq/ondemand # tail -v *
==> ignore_nice_load <==
1
==> powersave_bias <==
0
==> sampling_rate <==
500000
==> sampling_rate_max <==
250000000
==> sampling_rate_min <==
250000
==> up_threshold <==
80
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-26 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:11 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-01-26 14:06 Toralf Förster
2008-02-04 0:32 ` Andrew Morton
2008-02-04 0:36 ` Andrew Morton
2008-02-04 17:44 ` Pallipadi, Venkatesh
2008-02-04 19:18 ` 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=200801261946.54518.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®