linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Rik van Riel <riel@redhat.com>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	ShuoX Liu <shuox.liu@intel.com>,
	Boris Ostrovsky <boris.ostrovsky@amd.com>,
	Len Brown <len.brown@intel.com>,
	Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH 0/3] c-state governor changes
Date: Fri, 24 Aug 2012 05:11:08 +0100	[thread overview]
Message-ID: <20120824041108.GC3001@srcf.ucam.org> (raw)
In-Reply-To: <5036A67D.9090904@linux.intel.com>

On Thu, Aug 23, 2012 at 02:54:05PM -0700, Arjan van de Ven wrote:
> On 8/23/2012 2:11 PM, Rik van Riel wrote:
> > This patch set is mostly there to kick off a discussion in time
> > for Kernel Summit.  When running it on my laptop, with acpi_idle,
> > I see a promising change in powertop.
> 
> be careful with acpi_idle... that will remove most of the intermediate C states the platform has,
> so the policy engine no longer has good things to chose from.

Not inherently - intel_idle typically only exports 4 C states, and many 
ACPI platforms will provide the same number, especially when on battery.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2012-08-24  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 21:11 [RFC][PATCH 0/3] c-state governor changes Rik van Riel
2012-08-23 21:11 ` [RFC][PATCH 1/3] cpuidle: fix underflow in stddev calculation Rik van Riel
2012-08-23 21:13 ` [RFC][PATCH 2/3] cpuidle: find a typical recent sleep interval Rik van Riel
2012-08-23 21:13 ` [RFC][PATCH 3/3] cpuidle: count double the exit latency Rik van Riel
2012-08-23 21:54 ` [RFC][PATCH 0/3] c-state governor changes Arjan van de Ven
2012-08-24  2:57   ` Rik van Riel
2012-08-24  4:11   ` Matthew Garrett [this message]
2012-08-23 21:54 ` Arjan van de Ven

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=20120824041108.GC3001@srcf.ucam.org \
    --to=mjg@redhat.com \
    --cc=arjan@linux.intel.com \
    --cc=boris.ostrovsky@amd.com \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=shuox.liu@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).