LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-acpi@vger.kernel.org, Adam Belay <abelay@novell.com>,
	Shaohua Li <shaohua.li@intel.com>,
	Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/3]cpuidle take2: Core cpuidle infrastructure
Date: Tue, 27 Feb 2007 11:44:27 -0500	[thread overview]
Message-ID: <20070227164427.GB2223@redhat.com> (raw)
In-Reply-To: <20070222135257.A26335@unix-os.sc.intel.com>

On Thu, Feb 22, 2007 at 01:52:57PM -0800, Venkatesh Pallipadi wrote:

 > Announcing 'cpuidle', a new CPU power management infrastructure to manage
 > idle CPUs in a clean and efficient manner.
 > cpuidle separates out the drivers that can provide support for multiple types
 > of idle states and policy governors that decide on what idle state to use
 > at run time.
 > A cpuidle driver can support multiple idle states based on parameters like
 > varying power consumption, wakeup latency, etc (ACPI C-states for example).
 > A cpuidle governor can be usage model specific (laptop, server,
 > laptop on battery etc).
 > Main advantage of the infrastructure being, it allows independent development
 > of drivers and governors and allows for better CPU power management.

I played with this a little, and got puzzled.
My quad core box used exactly the same amount of power whether the
'ladder' governer was loaded & in use or not.  In both situations
it was exactly the same as a vanilla 2.6.20

I'd have expected it to use more until I loaded up 'ladder' to bring it
on par featurewise with 2.6.20.  What did I miss?

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-02-27 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 21:52 Venkatesh Pallipadi
2007-02-27 16:44 ` Dave Jones [this message]
2007-02-28  4:47   ` Pallipadi, Venkatesh
2007-02-28  6:59     ` Dave Jones

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=20070227164427.GB2223@redhat.com \
    --to=davej@redhat.com \
    --cc=abelay@novell.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    --subject='Re: [PATCH 1/3]cpuidle take2: Core cpuidle infrastructure' \
    /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

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).