From: Steven Rostedt <rostedt@goodmis.org>
To: Andi Kleen <ak@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
acpi-devel@lists.sourceforge.net, len.brown@intel.com,
nando@ccrma.Stanford.EDU, rlrevell@joe-job.com,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com, kr@cybsft.com,
tglx@linutronix.de, pluto@agmk.net, john.cooper@timesys.com,
bene@linutronix.de, dwalker@mvista.com,
trini@kernel.crashing.org, george@mvista.com, akpm@osdl.org
Subject: Re: [RFC][PATCH] Runtime switching of the idle function [take 2]
Date: Tue, 29 Nov 2005 10:42:34 -0500 [thread overview]
Message-ID: <1133278954.6328.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20051129145022.GE19515@wotan.suse.de>
On Tue, 2005-11-29 at 15:50 +0100, Andi Kleen wrote:
> On Tue, Nov 29, 2005 at 09:19:31AM -0500, Steven Rostedt wrote:
> > > And in practice the CPU will run so hot that only benchmarkers like it.
> >
> > Why would it run hot? What's the difference between polling and doing
> > other things. How many transistors does it take to poll?
>
> It will prevent the CPU from going into sleep states and essentially
> keep most of it enabled.
Well, there's one thing that my patch _does_ help with. (And it has
just helped me now). If you boot up with idle=poll and forget about it,
you can check what idle routine is being used and switch out of poll
without rebooting. (like I'm doing right now :-)
-- Steve
next prev parent reply other threads:[~2005-11-29 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051115090827.GA20411@elte.hu>
[not found] ` <1132336954.20672.11.camel@cmn3.stanford.edu>
[not found] ` <1132350882.6874.23.camel@mindpipe>
[not found] ` <1132351533.4735.37.camel@cmn3.stanford.edu>
[not found] ` <20051118220755.GA3029@elte.hu>
[not found] ` <1132353689.4735.43.camel@cmn3.stanford.edu>
[not found] ` <1132367947.5706.11.camel@localhost.localdomain>
[not found] ` <20051124150731.GD2717@elte.hu>
2005-11-25 20:56 ` [RFC][PATCH] Runtime switching to idle_poll (was: Re: 2.6.14-rt13) Steven Rostedt
2005-11-26 13:05 ` Ingo Molnar
2005-11-29 2:48 ` [RFC][PATCH] Runtime switching of the idle function [take 2] Steven Rostedt
2005-11-29 3:02 ` Andrew Morton
2005-11-29 3:42 ` Steven Rostedt
2005-11-29 4:01 ` Andrew Morton
2005-11-29 6:44 ` Ingo Molnar
2005-11-29 6:55 ` Nick Piggin
2005-11-29 18:05 ` Andi Kleen
2005-11-29 14:19 ` Steven Rostedt
2005-11-29 14:50 ` Andi Kleen
2005-11-29 15:42 ` Steven Rostedt [this message]
2005-12-02 1:27 ` Max Krasnyansky
2005-12-02 1:45 ` Andi Kleen
2005-12-03 2:17 ` Max Krasnyansky
2005-11-29 4:22 ` john stultz
2005-11-29 14:22 ` Steven Rostedt
2005-11-29 13:08 ` Pavel Machek
2005-12-18 15:26 ` Steven Rostedt
2005-11-29 19:37 Brown, Len
2005-11-29 19:53 ` Andi Kleen
2005-11-29 20:35 ` Lee Revell
2005-11-29 20:51 ` Andi Kleen
2005-11-29 23:55 ` Lee Revell
2005-11-30 1:06 ` Andi Kleen
2005-11-30 1:22 ` Lee Revell
2005-11-30 1:58 ` Andi Kleen
2005-11-30 2:19 ` john stultz
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=1133278954.6328.59.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bene@linutronix.de \
--cc=dwalker@mvista.com \
--cc=george@mvista.com \
--cc=john.cooper@timesys.com \
--cc=kr@cybsft.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
--cc=paulmck@us.ibm.com \
--cc=pluto@agmk.net \
--cc=rlrevell@joe-job.com \
--cc=tglx@linutronix.de \
--cc=trini@kernel.crashing.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