[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151110103438.GX17308@twins.programming.kicks-ass.net>
Date: Tue, 10 Nov 2015 11:34:38 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Juri Lelli <juri.lelli@...il.com>
Cc: Punit Agrawal <punit.agrawal@....com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Eduardo Valentin <edubezval@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Paul Turner <pjt@...gle.com>, Len Brown <len.brown@...el.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Andi Kleen <andi.kleen@...el.com>,
Rafael Wysocki <rafael.j.wysocki@...el.com>
Subject: Re: [RFC PATCH 0/3] CFS idle injection
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists