Re: [RFC PATCH v1 1/8] sched/cpufreq_schedutil: make use of DEADLINE utilization signal

2017-07-07 Thread Viresh Kumar
On 05-07-17, 09:58, Juri Lelli wrote: > SCHED_DEADLINE tracks active utilization signal with a per dl_rq > variable named running_bw. > > Make use of that to drive cpu frequency selection: add up FAIR and > DEADLINE contribution to get the required CPU capacity to handle both > requirements

Re: [RFC PATCH v1 1/8] sched/cpufreq_schedutil: make use of DEADLINE utilization signal

2017-07-07 Thread Viresh Kumar
On 05-07-17, 09:58, Juri Lelli wrote: > SCHED_DEADLINE tracks active utilization signal with a per dl_rq > variable named running_bw. > > Make use of that to drive cpu frequency selection: add up FAIR and > DEADLINE contribution to get the required CPU capacity to handle both > requirements

[RFC PATCH v1 1/8] sched/cpufreq_schedutil: make use of DEADLINE utilization signal

2017-07-05 Thread Juri Lelli
SCHED_DEADLINE tracks active utilization signal with a per dl_rq variable named running_bw. Make use of that to drive cpu frequency selection: add up FAIR and DEADLINE contribution to get the required CPU capacity to handle both requirements (while RT still selects max frequency).

[RFC PATCH v1 1/8] sched/cpufreq_schedutil: make use of DEADLINE utilization signal

2017-07-05 Thread Juri Lelli
SCHED_DEADLINE tracks active utilization signal with a per dl_rq variable named running_bw. Make use of that to drive cpu frequency selection: add up FAIR and DEADLINE contribution to get the required CPU capacity to handle both requirements (while RT still selects max frequency).