Hi,

On 18/01/19 10:34, Quentin Perret wrote:

Hi Rafael,

On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote:

quoted

On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret [off-list ref] wrote:

quoted

Hi Juri,

On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote:

quoted

On 10/01/19 11:05, Quentin Perret wrote:

[...]

quoted

quoted

+The idea behind introducing an EM is to allow the scheduler to evaluate the
+implications of its decisions rather than blindly applying energy-saving
+techniques that may have positive effects only on some platforms. At the same
+time, the EM must be as simple as possible to minimize the scheduler latency
+impact.
+
+In short, EAS changes the way CFS tasks are assigned to CPUs. When it is time

Not sure if we want to remark the fact that EAS is looking at CFS tasks
only ATM.

Oh, what's wrong about mentioning it ? I mean, it is a fact ATM ...

But it won't hurt to mention that it may cover other scheduling
classes in the future.  IOW, the scope limit is not fundamental.

Agreed, I can do that.

Oh, sorry, bad phrasing from my side. I meant that we should probably
state clearly somewhere that EAS deals with CFS only ATM, but extending
it to other classes (DEADLINE in particular) makes certainly sense and
people are welcome to experiment with that.

So, yeah, I agree with both of you. :-)