Re: [RFC PATCH v1 2/8] sched/deadline: move cpu frequency selection triggering points

From: Viresh Kumar
Date: Fri Jul 07 2017 - 03:21:13 EST


On 05-07-17, 09:58, Juri Lelli wrote:
> Since SCHED_DEADLINE doesn't track utilization signal (but reserves a
> fraction of CPU bandwidth to tasks admitted to the system), there is no
> point in evaluating frequency changes during each tick event.
>
> Move frequency selection triggering points to where running_bw changes.
>
> Co-authored-by: Claudio Scordino <claudio@xxxxxxxxxxxxxxx>
> Signed-off-by: Juri Lelli <juri.lelli@xxxxxxx>
> Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> Cc: Ingo Molnar <mingo@xxxxxxxxxx>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
> Cc: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> Cc: Luca Abeni <luca.abeni@xxxxxxxxxxxxxxx>
> ---
> Changes from RFCv0:
>
> - modify comment regarding periodic RT updates (Claudio)
> ---
> kernel/sched/deadline.c | 7 ++++---
> kernel/sched/sched.h | 12 ++++++------
> 2 files changed, 10 insertions(+), 9 deletions(-)

Reviewed-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>

--
viresh