Re: [RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

On Mon, Apr 10, 2017 at 12:38 PM, Brendan Jackman wrote: > Hi Rafael, > > On Mon, Apr 10 2017 at 00:10, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> Make the schedutil governor compute the initial (default) value of >> the

Re: [RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

On Mon, Apr 10, 2017 at 12:38 PM, Brendan Jackman wrote: > Hi Rafael, > > On Mon, Apr 10 2017 at 00:10, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> Make the schedutil governor compute the initial (default) value of >> the rate_limit_us sysfs attribute by multiplying the transition

Re: [RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

Hi Rafael, On Mon, Apr 10 2017 at 00:10, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Make the schedutil governor compute the initial (default) value of > the rate_limit_us sysfs attribute by multiplying the transition > latency by a multiplier depending on

Re: [RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

Hi Rafael, On Mon, Apr 10 2017 at 00:10, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Make the schedutil governor compute the initial (default) value of > the rate_limit_us sysfs attribute by multiplying the transition > latency by a multiplier depending on the policy and set by the >

[RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

From: Rafael J. Wysocki Make the schedutil governor compute the initial (default) value of the rate_limit_us sysfs attribute by multiplying the transition latency by a multiplier depending on the policy and set by the scaling driver (instead of using a constant for

[RFC/RFT][PATCH 1/2] cpufreq: schedutil: Use policy-dependent latency multupliers

From: Rafael J. Wysocki Make the schedutil governor compute the initial (default) value of the rate_limit_us sysfs attribute by multiplying the transition latency by a multiplier depending on the policy and set by the scaling driver (instead of using a constant for this purpose). That will