Re: [RFC PATCH 0/3] CFS idle injection
From: Punit Agrawal
Date: Mon Nov 09 2015 - 08:28:09 EST
Jacob Pan <jacob.jun.pan@xxxxxxxxxxxxxxx> writes:
> On Fri, 06 Nov 2015 16:50:15 +0000
> Punit Agrawal <punit.agrawal@xxxxxxx> wrote:
>> * idle injection once frequencies have been capped to the lowest
>> feasible values (as suggested in the cover letter)
> actually, I was suggesting to start considering idle injection once
> frequency capped to the energy efficient point, which can be much
> higher than the lowest frequency. The idea being, deep idle power is
> negligible compared to running power which allows near linear
> power-perf scaling for balanced workload.
> Below energy efficient frequency, continuous lowering frequency may
> lose disproportion performance vs. power. i.e. worse than linear.
I agree. I was making that assumption that with the ability to inject
idle states, there wouldn't be a need to expose the inefficient
Do you still see a reason to do that?
>> One question about the implementation in these patches - should the
>> implementation hook into pick_next_task in core instead of CFS? Higher
>> priority tasks might get in the way of idle injection.
> 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.
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/