From: Peter Zijlstra <peterz@infradead.org>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Paul Turner <pjt@google.com>, Len Brown <len.brown@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Andi Kleen <andi.kleen@intel.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [RFC PATCH 0/3] CFS idle injection
Date: Mon, 9 Nov 2015 15:15:34 +0100 [thread overview]
Message-ID: <20151109141534.GL17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <9hhbnb38jy4.fsf@e105922-lin.cambridge.arm.com>
On Mon, Nov 09, 2015 at 11:56:51AM +0000, Punit Agrawal wrote:
> Jacob Pan <jacob.jun.pan@linux.intel.com> writes:
> > My take is that RT and throttling will never go well together since they
> > are conflicting in principle.
>
> I am not sure I follow. If RT (or other higher priority classes) can't
> be throttled then the CPUs are not able to contribute towards
> constraining power consumption and hence temperature.
>
> This is especially true in certain platforms where tasks belong to the
> RT class to maintain user experience, e.g., audio and video.
Audio/Video playback generally doesn't take a _lot_ of time these days.
What is important though is _when_ it happens.
And media playback typically already has a very well defined and stable
cadence (24Hz or whatnot). What you want is for your idle injector to
sync up with that, not disrupt it.
For other workloads, missing a deadline is about as bad as destroying
the chip, complete system shutdown might be safer than getting delayed.
(The very tired scenario of a saw, a laser and your finger; you want to
shut down the entire machine rather than just cut off your finger.)
next prev parent reply other threads:[~2015-11-09 14:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 0:10 Jacob Pan
2015-11-03 0:10 ` [RFC PATCH 1/3] ktime: add a roundup function Jacob Pan
2015-11-03 0:10 ` [RFC PATCH 2/3] timer: relax tick stop in idle entry Jacob Pan
2015-11-03 0:10 ` [RFC PATCH 3/3] sched: introduce synchronized idle injection Jacob Pan
2015-11-03 13:31 ` Peter Zijlstra
2015-11-03 14:16 ` Jacob Pan
2015-11-03 16:45 ` Jacob Pan
2015-11-05 10:09 ` Peter Zijlstra
2015-11-05 14:22 ` Arjan van de Ven
2015-11-05 14:33 ` Peter Zijlstra
2015-11-05 14:48 ` Peter Zijlstra
2015-11-05 15:28 ` Arjan van de Ven
2015-11-05 16:52 ` Peter Zijlstra
2015-11-05 18:55 ` Thomas Gleixner
2015-11-05 18:47 ` Thomas Gleixner
2015-11-05 15:32 ` Jacob Pan
2015-11-05 16:06 ` Arjan van de Ven
2015-11-05 19:27 ` Jacob Pan
2015-11-05 19:32 ` Jacob Pan
2015-11-05 13:59 ` Peter Zijlstra
2015-11-05 23:36 ` Jacob Pan
2015-11-06 7:45 ` Peter Zijlstra
2015-11-06 23:49 ` Jacob Pan
2015-11-10 0:19 ` Jacob Pan
2015-11-04 6:06 ` [RFC PATCH 0/3] CFS " Eduardo Valentin
2015-11-04 16:58 ` Jacob Pan
2015-11-04 17:05 ` Srinivas Pandruvada
2015-11-04 18:43 ` Eduardo Valentin
2015-11-05 10:12 ` Peter Zijlstra
2015-11-06 16:50 ` Punit Agrawal
2015-11-06 19:18 ` Jacob Pan
2015-11-09 11:56 ` Punit Agrawal
2015-11-09 14:15 ` Peter Zijlstra [this message]
2015-11-09 14:43 ` Jacob Pan
2015-11-10 10:07 ` Juri Lelli
2015-11-10 10:34 ` Peter Zijlstra
2015-11-10 10:56 ` Juri Lelli
2015-11-09 14:36 ` Jacob Pan
2015-11-06 18:30 ` Dietmar Eggemann
2015-11-06 19:10 ` Jacob Pan
2015-11-06 21:55 ` Dietmar Eggemann
2015-11-09 21:23 ` Jacob Pan
2015-11-09 21:45 ` Peter Zijlstra
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=20151109141534.GL17308@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi.kleen@intel.com \
--cc=arjan@linux.intel.com \
--cc=edubezval@gmail.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjt@google.com \
--cc=punit.agrawal@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.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
Powered by JetHome