From: Dave Jones <davej@redhat.com>
Subject: Re: ondemand as default governor
Date: Wed, 7 Mar 2007 02:02:08 -0500
Message-ID: <20070307070208.GB15453@redhat.com>
References: <1172770914.10619.587.camel@d36.suse.de>
	<200703070124.29058.lenb@kernel.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <200703070124.29058.lenb@kernel.org>
Sender: cpufreq-bounces@lists.linux.org.uk
Errors-To: cpufreq-bounces+glkc-cpufreq=m.gmane.org+glkc-cpufreq=m.gmane.org@lists.linux.org.uk
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Len Brown <lenb@kernel.org>
Cc: cpufreq@lists.linux.org.uk

On Wed, Mar 07, 2007 at 01:24:28AM -0500, Len Brown wrote:
 > On Thursday 01 March 2007 12:41, Thomas Renninger wrote:
 > > I just read in drivers/cpufreq/Kconfig:
 > > 
 > > # Note that it is not currently possible to set the other governors
 > > (such as ondemand)
 > > # as the default, since if they fail to initialise, cpufreq will be
 > > # left in an undefined state.
 > > 
 > > Is this a bigger problem to solve?
 > > Is there already someone working/thinking on/about a solution?
 > > 
 > > Allowing this would be convenient...
 > 
 > Yes, it would, then we could delete the other governors,
 > and then delete the concept of multiple governors alltogether.

It's not feasible unless you have a way of making various
older CPUs transition faster.  Ondemand on longhaul,powernow-k6,longrun,
elanfreq, as well as lots of non-x86 implementations is just not
a feasible option.

However.. conservative might be.  I'd still like to see conservative
folded into ondemand sometime, and just be a module param.

	Dave

-- 
http://www.codemonkey.org.uk