On Mon, May 4, 2015 at 4:27 PM, Rafael J. Wysocki wrote:
> On Monday, May 04, 2015 03:10:37 PM Michael Turquette wrote:
>> This series implements an event-driven cpufreq governor that scales cpu
>> frequency as a function of cfs runqueue utilization. The intent of this RFC
>> is
>> to get some
On Mon, May 4, 2015 at 4:27 PM, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Monday, May 04, 2015 03:10:37 PM Michael Turquette wrote:
This series implements an event-driven cpufreq governor that scales cpu
frequency as a function of cfs runqueue utilization. The intent of this RFC
is
to
On Monday, May 04, 2015 03:10:37 PM Michael Turquette wrote:
> This series implements an event-driven cpufreq governor that scales cpu
> frequency as a function of cfs runqueue utilization. The intent of this RFC is
> to get some discussion going about how the scheduler can become the policy
>
This series implements an event-driven cpufreq governor that scales cpu
frequency as a function of cfs runqueue utilization. The intent of this RFC is
to get some discussion going about how the scheduler can become the policy
engine for selecting cpu frequency, what limitations exist and what
On Monday, May 04, 2015 03:10:37 PM Michael Turquette wrote:
This series implements an event-driven cpufreq governor that scales cpu
frequency as a function of cfs runqueue utilization. The intent of this RFC is
to get some discussion going about how the scheduler can become the policy
engine
This series implements an event-driven cpufreq governor that scales cpu
frequency as a function of cfs runqueue utilization. The intent of this RFC is
to get some discussion going about how the scheduler can become the policy
engine for selecting cpu frequency, what limitations exist and what
6 matches
Mail list logo