All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Pallipadi, Venkatesh" <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>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: [PATCH 1/3]cpuidle take2: Core cpuidle infrastructure
Date: Wed, 28 Feb 2007 01:59:32 -0500	[thread overview]
Message-ID: <20070228065932.GA23678@redhat.com> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A845401540255@scsmsx413.amr.corp.intel.com>

On Tue, Feb 27, 2007 at 08:47:55PM -0800, Pallipadi, Venkatesh wrote:

 > >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?
 > 
 > Quad core what platform?

Glenwood

 > How many C-states are supported in this platform?

Garg, only C1.  That explains a lot.

 > Current ladder is mostly like Policy embedded in ACPI today. But, Adam
 > has
 > been working on different policies that we want to experiment with as we
 > go along.

ok.

		Dave


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

      reply	other threads:[~2007-02-28  7:00 UTC|newest]

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

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=20070228065932.GA23678@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 \
    /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.