From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org,
fweisbec@gmail.com, amit.kucheria@linaro.org,
rusty@rustcorp.com.au, tglx@linutronix.de,
Arjan van de Ven <arjan@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V6 0/2] tracing, perf: cpu hotplug trace events
Date: Thu, 03 Mar 2011 17:42:56 -0500 [thread overview]
Message-ID: <1299192176.6376.47.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <201103022307.46694.trenn@suse.de>
On Wed, 2011-03-02 at 23:07 +0100, Thomas Renninger wrote:
> I doubt cpu offlining is the proper instrument to save power.
> You want to prevent the CPU of being used by ripping it out from scheduler decisions and
> make sure it doesn't get interrupts by offlining. But the (latency) price is high.
I could imagine that a server could use this for power savings to take
down all but 1 CPU on off hours. When it knows its not going to get much
action but still needs to remain online. Then just before peak times
begin, online the other CPUs.
But anything more dynamic than that, I can't see it really worth it. As
the latency to bring the other CPU online, may miss a peak when it was
needed.
-- Steve
next prev parent reply other threads:[~2011-03-03 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 16:05 Vincent Guittot
2011-03-02 7:56 ` Ingo Molnar
2011-03-02 10:57 ` Thomas Renninger
2011-03-02 19:02 ` Vincent Guittot
2011-03-02 22:07 ` Thomas Renninger
2011-03-03 22:42 ` Steven Rostedt [this message]
2011-03-07 11:25 ` Amit Kucheria
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=1299192176.6376.47.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=amit.kucheria@linaro.org \
--cc=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®