Message-ID: <5577D7DB.5020802@linaro.org>
Date: Wed, 10 Jun 2015 14:23:23 +0800
From: Alex Shi <alex.shi@linaro.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Michael Turquette <mturquette@linaro.org>, peterz@infradead.org,
        mingo@kernel.org
CC: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
        preeti@linux.vnet.ibm.com, Morten.Rasmussen@arm.com, riel@redhat.com,
        efault@gmx.de, nicolas.pitre@linaro.org, daniel.lezcano@linaro.org,
        dietmar.eggemann@arm.com, vincent.guittot@linaro.org,
        amit.kucheria@linaro.org, juri.lelli@arm.com, rjw@rjwysocki.net,
        viresh.kumar@linaro.org, ashwin.chaugule@linaro.org,
        abelvesa@gmail.com
Subject: Re: [PATCH RFC v2 4/4] sched: cpufreq_cfs: pelt-based cpu frequency
 scaling
References: <1431396795-32439-1-git-send-email-mturquette@linaro.org> <1431396795-32439-5-git-send-email-mturquette@linaro.org>
In-Reply-To: <1431396795-32439-5-git-send-email-mturquette@linaro.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1010
Lines: 26


On 05/12/2015 10:13 AM, Michael Turquette wrote:
> This governor is event-driven. There is no polling loop to check cpu
> idle time nor any other method which is unsynchronized with the
> scheduler. The entry points for this policy are in fair.c:
> enqueue_task_fair, dequeue_task_fair and task_tick_fair.
> 
> This policy is implemented using the cpufreq governor interface for two
> main reasons:
> 
> 1) re-using the cpufreq machine drivers without using the governor
> interface is hard.
> 
> 2) using the cpufreq interface allows us to switch between the
> scheduler-driven policy and legacy cpufreq governors such as ondemand at
> run-time. This is very useful for comparative testing and tuning.

Hi, Mike,

Did you have some testing data with your patch?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/