cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Capit <capitn@free.fr>
To: Len Brown <lenb@kernel.org>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: ondemand: cpu load calculation with kernel processus
Date: Thu, 31 May 2007 20:57:51 -0500	[thread overview]
Message-ID: <20070531205751.2f56da4d@localhost.localdomain> (raw)
In-Reply-To: <200705312057.45963.lenb@kernel.org>

On Thu, 31 May 2007 20:57:45 -0400
Len Brown <lenb@kernel.org> wrote:

> On Thursday 31 May 2007 17:57, Nicolas Capit wrote:
> > Hello,
> > 
> > I am running a Debian unstable with a kernel 2.6.21-1-686 and using
> > modules powernow_k8 and cpufreq_ondemand.
> > 
> > My configuration with the ondemand governor seems to work very well
> > except when my cpu is busy by the kernel processus kcryptd. The cpu is
> > 100% busy but the frequency is not increased.
> > (I am using the module dm_crypt to encrypt my home filesystem)
> > 
> > So my question is:
> > Does the ondemand governor calculate the load of the machine with user
> > level and *kernel* level processus?
> 
> both user and kernel time should count as busy time.
> 
> do the cpu stats exposed by top show that you have idle time available?

Ok I am sorry for the noise :-(
My program that get the CPU stats is buggy... with top, effectively the
CPU is 0% idle but 10%us and 90%wa
(wa : Amount of time the CPU has been waiting for I/O to complete.)

Except if increasing the CPU frequency will reduce I/O wait time, the
cpufreq_ondemand works well...


> 
> -Len
> 

      reply	other threads:[~2007-06-01  1:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 21:57 ondemand: cpu load calculation with kernel processus Nicolas Capit
2007-06-01  0:57 ` Len Brown
2007-06-01  1:57   ` Nicolas Capit [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=20070531205751.2f56da4d@localhost.localdomain \
    --to=capitn@free.fr \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=lenb@kernel.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