public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Machine no longer enters C3 on 2.6.11-rc1-bk
Date: 20 Jan 2005 23:30:53 -0500	[thread overview]
Message-ID: <1106281843.2399.140.camel@d845pe> (raw)
In-Reply-To: <41EFC117.9050202-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>

On Thu, 2005-01-20 at 09:32, Rich Townsend wrote:

> Gak, I just read the wiki, and USB was the culprit. But that doesn't 
> explain why I'm not seeing any transitions to C1, even under full load.

This is normal for the current code -- we run C1 16 times and promote,
but if C2 latency is very low, we never demote to C1:

[root@d600 root]#  cat  /proc/acpi/processor/CPU0/power
active state:            C4
max_cstate:              C8
bus master activity:     00000000
states:
 C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] 
 C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[00266192]
 C3: type[C3] promotion[C4] demotion[C2] latency[085] usage[00028664]
*C4: type[C3] promotion[--] demotion[C3] latency[185] usage[00359811]




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-21  4:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 10:40 Machine no longer enters C3 on 2.6.11-rc1-bk Pavel Machek
     [not found] ` <20050120104033.GA25889-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-20 10:59   ` Fred Labrosse
     [not found]     ` <16879.36609.94551.926755-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2005-01-20 10:59       ` Pavel Machek
     [not found]         ` <20050120105911.GF1452-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-20 14:25           ` Rich Townsend
     [not found]             ` <41EFBF4B.80206-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-01-20 14:32               ` Rich Townsend
     [not found]                 ` <41EFC117.9050202-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-01-21  4:30                   ` Len Brown [this message]
2005-01-20 11:01       ` Pavel Machek
2005-01-20 11:06       ` Pavel Machek

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=1106281843.2399.140.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.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