MIME-Version: 1.0
In-Reply-To: <20151109141534.GL17308@twins.programming.kicks-ass.net>
References: <1446509428-5616-1-git-send-email-jacob.jun.pan@linux.intel.com>
	<20151104060654.GC8850@localhost.localdomain>
	<20151104085830.010e69f8@yairi>
	<20151105101218.GB3604@twins.programming.kicks-ass.net>
	<9hhvb9f843c.fsf@e105922-lin.cambridge.arm.com>
	<20151106111838.6172085d@icelake>
	<9hhbnb38jy4.fsf@e105922-lin.cambridge.arm.com>
	<20151109141534.GL17308@twins.programming.kicks-ass.net>
Date: Tue, 10 Nov 2015 10:07:35 +0000
Message-ID: <CAE-h8tFn-rfs0yUdEqkZGOVPw0ZaseuPm94mnPvnV=KPL5iVsQ@mail.gmail.com>
Subject: Re: [RFC PATCH 0/3] CFS idle injection
From: Juri Lelli <juri.lelli@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Punit Agrawal <punit.agrawal@arm.com>,
        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>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2079
Lines: 50

Hi,

On 9 November 2015 at 14:15, Peter Zijlstra <peterz@infradead.org> wrote:
> 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.
>

Do you think that using SCHED_DEADLINE here would be completely
foolish? I mean, we would have the duty_cycle/period thing for free, it
would be know to the scheduler (as to maybe address Thomas' concerns)
and we could think to make idle injection part of system analysis (for
the soft-RT use cases).

Thanks,

- Juri

> 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.)
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/