From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Never in C3
Date: Tue, 15 Jun 2004 18:39:14 +0100 [thread overview]
Message-ID: <1087321154.10618.0.camel@tyrosine> (raw)
In-Reply-To: <16589.41686.480893.225338-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
On Mon, 2004-06-14 at 14:06 +0100, Fred Labrosse wrote:
> *C1: promotion[C2] demotion[--] latency[000] usage[02058670]
> C2: promotion[C3] demotion[C1] latency[020] usage[19743630]
> C3: promotion[--] demotion[C2] latency[200] usage[00000000]
My recollection is that if the latency is larger than 100, Linux will
never use C3.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
next prev parent reply other threads:[~2004-06-15 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 13:06 Never in C3 Fred Labrosse
[not found] ` <16589.41686.480893.225338-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2004-06-14 14:33 ` Karol Kozimor
[not found] ` <20040614143312.GA16952-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-06-15 13:35 ` Fred Labrosse
[not found] ` <16590.64317.405885.159934-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2004-06-15 15:32 ` Karol Kozimor
2004-06-15 17:39 ` Matthew Garrett [this message]
[not found] ` <1087321154.10618.0.camel-myFlNLNQP+Q@public.gmane.org>
2004-06-15 19:03 ` Nate Lawson
2004-06-16 11:36 ` Frank Mehnert
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=1087321154.10618.0.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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