Date: Tue, 10 Nov 2015 10:56:34 +0000
From: Juri Lelli <juri.lelli@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Juri Lelli <juri.lelli@gmail.com>, 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>
Subject: Re: [RFC PATCH 0/3] CFS idle injection
Message-ID: <20151110105634.GA8516@e106622-lin>
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>
 <CAE-h8tFn-rfs0yUdEqkZGOVPw0ZaseuPm94mnPvnV=KPL5iVsQ@mail.gmail.com>
 <20151110103438.GX17308@twins.programming.kicks-ass.net>
MIME-Version: 1.0
In-Reply-To: <20151110103438.GX17308@twins.programming.kicks-ass.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1406
Lines: 34

On 11/10/15, Peter Zijlstra wrote:
> On Tue, Nov 10, 2015 at 10:07:35AM +0000, Juri Lelli wrote:
> > 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).
> 
> DEADLINE would be awesome, but I think we need work on two fronts before
> we can really sell it as the awesome that it is ;-)
> 
>  - greedy and or statistical bounds
>  - !priv
> 
> The first is such that we can better deal with the erratic nature of
> media decode without going full worst case on it, and the second just
> makes it so much more accessible.
> 

Right. For the first point I think we just need to make our off-line
calculation right, not that we need to modify implementation. On the
second point we need more work yes. Also, another thing that is missing
is frequency (uarch) scaling for reservations parameters, something alike
what we are doing for CFS; this last point might be solved sooner :-).

Thanks,

- Juri

--
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/