From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Toralf.=?iso-8859-1?Q?F=F6rster_=3Ctoralf=2Efoerster=40gmx=2Ede=3E?=@snowy.in.ibm.com
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
a.p.zijlstra@chello.nl, dhaval@linux.vnet.ibm.com
Subject: Re: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date: Sun, 27 Jan 2008 20:16:10 +0530 [thread overview]
Message-ID: <20080127144610.GA25632@linux.vnet.ibm.com> (raw)
In-Reply-To: <200801261946.54518.toralf.foerster@gmx.de>
On Sat, Jan 26, 2008 at 07:46:51PM +0100, Toralf Förster wrote:
>
> 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
Hi Toralf,
Can you list the o/p you see for overall cpu usage? You should
see something like below right at the top of the o/p:
top - 20:03:59 up 12 days, 21:39, 18 users, load average: 0.22, 0.20, 0.25
Tasks: 200 total, 5 running, 193 sleeping, 0 stopped, 2 zombie
Cpu(s): 2.6% us, 1.3% sy, 0.0% ni, 96.0% id, 0.0% wa, 0.0% hi, 0.0% si, 0.0% st
The third line (giving overall cpu usage stats) is what is interesting here.
If you have more than one cpu, you can get cpu usage stats for each cpu
in top by pressing 1. Can you provide this information with and w/o
CONFIG_FAIR_GROUP_SCHED?
If I am not mistaken, cpu ondemand gov goes by the cpu idle time stats,
which should not be affected by FAIR_GROUP_SCHED. I will lookaround for
other possible causes.
--
Regards,
vatsa
next prev parent reply other threads:[~2008-01-27 14:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:11 (ondemand) CPU governor regression between 2.6.23 and 2.6.24 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster
2008-01-27 14:46 ` Srivatsa Vaddagiri [this message]
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=20080127144610.GA25632@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=Toralf.=?iso-8859-1?Q?F=F6rster_=3Ctoralf=2Efoerster=40gmx=2Ede=3E?=@snowy.in.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=mingo@elte.hu \
/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