From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Brodowski Subject: Re: Implementation of fast-up algorithm in ondemand governor Date: Thu, 6 Nov 2003 07:50:00 +0100 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <20031106065000.GA4188@brodo.de> References: Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces@www.linux.org.uk Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Moore, Robert" Cc: cpufreq@www.linux.org.uk On Wed, Nov 05, 2003 at 02:34:07PM -0800, Moore, Robert wrote: > > > Will this simple change implement the fast-up algorithm correctly? "the" fast-up algorithm? Well, it surely _is_ a fast-up algorithm what you propose: > - if (idle_ticks < (DBS_RATE / 5)) > - cpufreq_driver_target(cpu_dbs_info[cpu].cur_policy, > - cpu_dbs_info[cpu].cur_policy->cur + 1, > - CPUFREQ_RELATION_L); > > + if (idle_ticks < (DBS_RATE / 5)) > + cpufreq_driver_target(cpu_dbs_info[cpu].cur_policy, > + cpu_dbs_info[cpu].cur_policy->max, > + CPUFREQ_RELATION_L); However, please set CPUFREQ_RELATION_H here -- you don't want to go higher than cur_policy->max. Dominik