Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267953AbUJSFGd (ORCPT ); Tue, 19 Oct 2004 01:06:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267961AbUJSFGd (ORCPT ); Tue, 19 Oct 2004 01:06:33 -0400 Received: from willy.net1.nerim.net ([62.212.114.60]:19461 "EHLO willy.net1.nerim.net") by vger.kernel.org with ESMTP id S267953AbUJSFGb (ORCPT ); Tue, 19 Oct 2004 01:06:31 -0400 Date: Tue, 19 Oct 2004 07:06:17 +0200 From: Willy Tarreau To: Alexander Clouter Cc: "Pallipadi, Venkatesh" , Con Kolivas , cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cpufreq_ondemand Message-ID: <20041019050616.GI19761@alpha.home.local> References: <88056F38E9E48644A0F562A38C64FB60031DA073@scsmsx403.amr.corp.intel.com> <20041018083905.GC3311@inskipp.digriz.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041018083905.GC3311@inskipp.digriz.org.uk> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1314 Lines: 27 Hi, On Mon, Oct 18, 2004 at 09:39:05AM +0100, Alexander Clouter wrote: > I'm all for "this really should be done in userspace", but for something like > this I have a nagging feeling that its neater in kernel-space. Of course the > userspace one has the advantage (I think cpufreqd does it) that you can > decide if you want to increase the freq depending on what applications are > running. Well, I've used a very simple daemon I wrote for more than a year now on a vaio, and considering that I sometimes wanted to change it or even stop it, I clearly prefer it in userspace than in kernel. It was so convenient to issue a "killall cpufrqd" whenever I wanted 'time' to return accurate values on a particular process, that I cannot imagine what it would have been if it had been in the kernel. Moreover, the vaio was unreliable with certain intermediate frequencies, and it too me a lot of time to discover this (burnBX was the only reliable trigger). I simply had to change a few lines in my daemon to use different frequencies and that was all. Cheers, Willy - 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/