All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: akolisek@linuxx.hyperlinx.cz
Cc: cpufreq@www.linux.org.uk
Subject: Re: [Bug 8243] Problem with Throttling and CPU power state
Date: Mon, 27 Aug 2007 22:27:11 +0200	[thread overview]
Message-ID: <46D3339F.3090203@interia.pl> (raw)
In-Reply-To: <20070827194633.5278D108078@picon.linux-foundation.org>

> This bug is present in kernel 2.6.22(.1,2,3,4,5) too :(
I don't get it. Where is the bug?
> Why my CPU is not in C1 state, when works on 100%? And where is C0 state?
C0 means that CPU is working so it isn't listed.
I think that You have misunderstood this file. It isn't printing current 
CPU state. It is listing all available sleep states in order from 
low latency and higher power consumption to high latency and lower power 
consumption. Star means state that will be used when CPU become idle. 
"Latency" means time needed to enter sleep state and time needed to wakeup 
when something will happen (interrupt or BM DMA for example). So it is 
perfectly OK to use C4 when there it isn't much to do and C2 when CPU is 
spending less time sleeping.
Kernel compilation isn't causing 100% CPU usage. Processor is sleeping 
during I/O wait. Well, unless You are using -j2 or higher.
> state T4 is activated, but only a few seconds and then it goes back to T0. Is
> this ok?
Yes. BIOS option "use throttling to rescue CPU when it is overheating" 
interfering.

Regards
Rafa³

----------------------------------------------------------------------
Jak najszybciej dostac sie na wymarzona plaze?
Znajdz trase ekspresowa

>>>http://link.interia.pl/f1b0c

  reply	other threads:[~2007-08-27 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8243-3570@http.bugzilla.kernel.org/>
2007-07-14  3:42 ` [Bug 8243] Problem with Throttling and CPU power state bugme-daemon
2007-08-27 19:46 ` bugme-daemon
2007-08-27 20:27   ` Rafał Bilski [this message]
2007-08-27 20:18 ` bugme-daemon
2007-08-27 20:19 ` bugme-daemon
     [not found] <bug-8243-27@http.bugzilla.kernel.org/>
     [not found] ` <20070827194633.44C5010807D@picon.linux-foundation.org>
2007-08-27 20:01   ` Andrew Morton
2007-08-27 20:19     ` Dave Jones
2007-03-21 16:22 bugme-daemon
  -- strict thread matches above, loose matches on Subject: below --
2007-03-21  8:28 bugme-daemon
2007-03-21  8:07 bugme-daemon

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=46D3339F.3090203@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=akolisek@linuxx.hyperlinx.cz \
    --cc=cpufreq@www.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.