From: Pavel Machek <pavel@ucw.cz>
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>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: RFC: A proposal for power capping through forced idle in the Linux Kernel
Date: Wed, 23 Dec 2009 10:52:39 +0100 [thread overview]
Message-ID: <20091223095239.GD24181@elf.ucw.cz> (raw)
In-Reply-To: <4352991a0912221315y5ba409cbh26baa5937cdf2f76@mail.gmail.com>
Hi!
> > OTOH realtime people already have tools you could make good use of:
> > your power capping approach looks like 'high priority idle task that
> > needs to run for 2 seconds every 5 seconds' or something...
> >
> > Talk to rt people?
>
> At the core of it, you are correct. However, in our implementation it
> also avoids running when the system is already idle and operates at
> much finer granularities than seconds.
Seconds were examples, I suspect rt kernels need lower granularities,
to.
> Which specific tools are you referring to? Real-time Linux as a whole
> is a trade off: one gets predictable latency in exchange for some
> performance. Any specific contacts that I should direct my inquiries
> to?
I guess Peter and Ingo (added to the Cc)....
Anyway, I guess that what you really want is to be able to change
priority of the idle threads, even making them realtime...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-12-23 9:52 UTC|newest]
Thread overview: 22+ 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:51 ` tytso
2009-12-15 0:42 ` Salman Qazi
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-15 10:29 ` Vaidyanathan Srinivasan
2009-12-15 11:50 ` Vaidyanathan Srinivasan
2009-12-15 21:00 ` Salman Qazi
2009-12-15 20:50 ` Salman Qazi
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:57 ` Arjan van de Ven
2009-12-18 17:04 ` Pavel Machek
2009-12-22 21:10 ` Salman Qazi
2009-12-23 9:49 ` Pavel Machek
2009-12-21 8:57 ` Pavel Machek
2009-12-22 21:15 ` Salman Qazi
2009-12-23 9:52 ` Pavel Machek [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=20091223095239.GD24181@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=mrubin@google.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox