From: Arjan van de Ven <arjan@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Salman Qazi <sqazi@google.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, svaidy@linux.vnet.ibm.com,
linux-pm@lists.linux-foundation.org, csadler@google.com,
ranjitm@google.com, kenchen@google.com, dawnchen@google.com
Subject: Re: [PATCH 0/3] [idled]: Idle Cycle Injector for power capping
Date: Mon, 19 Apr 2010 18:00:32 -0700 [thread overview]
Message-ID: <20100419180032.15586a90@infradead.org> (raw)
In-Reply-To: <1271703701.1676.235.camel@laptop>
On Mon, 19 Apr 2010 21:01:41 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> Right, so the IBM folks who were looking at power aware scheduling
> were working on an interface to quantify the amount of power to save.
>
> But their approach, was an extension of the regular power aware
> load-balancer, which basically groups tasks onto sockets so that whole
> sockets can go idle.
>
> However Arjan explained to me that your approach, which idles the
> whole machine, has the advantage that also memory banks can go into
> idle mode and save power.
>
> Still in the interest to cut back on power-saving interfaces it would
> be nice to see if there is anything we can do to merge these things,
> but I really haven't thought much about that yet.
one correction, this is not about power *saving*, it is about power
*capping*. Power capping is pretty much energy inefficient by
definition (and surely in practice), but it's about dealing with
reality about underdimensioned airconditioning or voltage rails....
Due to the reality that socket offlining isn't as good as idle
insertion.. I rather focus on the later...
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2010-04-20 0:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 0:08 [PATCH 0/3] [idled]: Idle Cycle Injector for power capping Salman
2010-04-14 0:08 ` [PATCH 1/3] [kidled]: introduce kidled Salman
2010-04-14 9:49 ` Andi Kleen
2010-04-14 15:41 ` Salman Qazi
2010-04-15 7:46 ` Peter Zijlstra
2010-04-14 0:08 ` [PATCH 2/3] [kidled]: Add eager injection Salman
2010-04-14 0:08 ` [PATCH 3/3] [kidled]: Introduce power capping priority and LB awareness Salman
2010-04-15 7:51 ` [PATCH 0/3] [idled]: Idle Cycle Injector for power capping Peter Zijlstra
2010-04-17 17:08 ` tytso
2010-04-17 17:57 ` Arjan van de Ven
2010-04-17 19:51 ` Peter Zijlstra
2010-04-19 17:20 ` Salman Qazi
2010-04-19 19:01 ` Peter Zijlstra
2010-04-20 1:00 ` Arjan van de Ven [this message]
2010-04-20 5:00 ` Vaidyanathan Srinivasan
2010-04-20 4:50 ` Vaidyanathan Srinivasan
2010-04-20 17:52 ` Salman Qazi
2010-04-21 5:08 ` Arjan van de Ven
2010-04-22 1:32 ` Mike Chan
2010-04-22 8:21 ` Peter Zijlstra
2010-04-22 19:02 ` Vaidyanathan Srinivasan
2010-04-17 16:40 ` 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=20100419180032.15586a90@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=csadler@google.com \
--cc=dawnchen@google.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=ranjitm@google.com \
--cc=sqazi@google.com \
--cc=svaidy@linux.vnet.ibm.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).