lkml.org 
[lkml]   [2008]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date

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
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2008-01-26 19:49    [W:0.089 / U:0.348 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site