From: Andi Kleen <andi@firstfloor.org>
To: Salman Qazi <sqazi@google.com>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Michael Rubin <mrubin@google.com>,
Taliver Heath <taliver@google.com>,
lenb@kernel.org
Subject: Re: RFC: A proposal for power capping through forced idle in the Linux Kernel
Date: Tue, 15 Dec 2009 00:21:07 +0100 [thread overview]
Message-ID: <876389xhuk.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4352991a0912141511k7f9b8b79y767c693a4ff3bc2b@mail.gmail.com> (Salman Qazi's message of "Mon, 14 Dec 2009 15:11:47 -0800")
Salman Qazi <sqazi@google.com> writes:
>
> We'd like to get as much of our stuff upstream as we can. Given that
> this is a somewhat sizable chunk of work, it would be impolite of me
> to just send out a bunch of patches without hearing the concerns of
> the community. What are your thoughts on our design and what do we
> need to change to get this to be more acceptable to the community? I
> also would like to know if there are any existing pieces of
> infrastructure that this can utilize.
There were a lot of discussions on this a few months ago in context
of the ACPI 4 "power aggregator" which is a similar (perhaps
slightly less sophisticated) concept.
While there was a lot of talk about teaching the scheduler about this
the end result was just a driver which just starts real time threads
and then idles in them. This is in current mainline.
It might be a good idea to review these discussions in the archives.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-12-14 23:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 23:11 RFC: A proposal for power capping through forced idle in the Linux Kernel Salman Qazi
2009-12-14 23:21 ` Andi Kleen
2009-12-14 23:21 ` Andi Kleen [this message]
2009-12-14 23:51 ` tytso
2009-12-14 23:51 ` tytso
2009-12-15 0:42 ` Salman Qazi
2009-12-15 0:42 ` Salman Qazi
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:48 ` Peter Zijlstra
2009-12-15 0:19 ` Arjan van de Ven
2009-12-15 0:36 ` Salman Qazi
2009-12-15 1:06 ` Arjan van de Ven
2009-12-15 20:15 ` Salman Qazi
2009-12-17 11:01 ` Arjan van de Ven
2009-12-17 11:01 ` Arjan van de Ven
2009-12-15 20:15 ` Salman Qazi
2009-12-15 1:06 ` Arjan van de Ven
2009-12-15 10:29 ` Vaidyanathan Srinivasan
2009-12-15 11:50 ` Vaidyanathan Srinivasan
2009-12-15 11:50 ` Vaidyanathan Srinivasan
2009-12-15 21:00 ` Salman Qazi
2009-12-15 21:00 ` Salman Qazi
2009-12-15 20:50 ` Salman Qazi
2009-12-15 20:50 ` Salman Qazi
2009-12-15 10:29 ` Vaidyanathan Srinivasan
2009-12-15 0:36 ` Salman Qazi
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:57 ` Arjan van de Ven
2009-12-22 19:57 ` Arjan van de Ven
2009-12-15 0:19 ` Arjan van de Ven
2009-12-18 17:04 ` Pavel Machek
2009-12-18 17:04 ` Pavel Machek
2009-12-22 21:10 ` Salman Qazi
2009-12-23 9:49 ` Pavel Machek
2009-12-23 9:49 ` Pavel Machek
2009-12-22 21:10 ` Salman Qazi
2009-12-21 8:57 ` Pavel Machek
2009-12-22 21:15 ` Salman Qazi
2009-12-22 21:15 ` Salman Qazi
2009-12-23 9:52 ` Pavel Machek
2009-12-23 9:52 ` Pavel Machek
2009-12-21 8:57 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-12-14 23:11 Salman Qazi
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=876389xhuk.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mrubin@google.com \
--cc=sqazi@google.com \
--cc=taliver@google.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.