mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Alexander Clouter <alex-kernel@digriz.org.uk>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	Con Kolivas <kernel@kolivas.org>,
	cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq_ondemand
Date: Tue, 19 Oct 2004 07:06:17 +0200	[thread overview]
Message-ID: <20041019050616.GI19761@alpha.home.local> (raw)
In-Reply-To: <20041018083905.GC3311@inskipp.digriz.org.uk>

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


  reply	other threads:[~2004-10-19  5:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  4:56 Pallipadi, Venkatesh
2004-10-18  8:39 ` Alexander Clouter
2004-10-19  5:06   ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-18 22:48 Pallipadi, Venkatesh
2004-10-18 23:18 ` Alexander Clouter
2004-10-17 22:29 Alexander Clouter
2004-10-17 22:35 ` Con Kolivas
2004-10-17 22:44   ` Alexander Clouter
2004-10-19 18:22   ` Bruno Ducrot
2004-10-20  5:03   ` Andre Eisenbach
2004-10-20  7:35     ` Len Brown
2004-10-20 14:30       ` Dominik Brodowski
2004-10-20 21:03         ` Len Brown
2004-10-20 21:18           ` Dominik Brodowski
2004-10-18  7:20 ` Dominik Brodowski
2004-10-18  8:12   ` Mattia Dongili
2004-10-18  8:25   ` Alexander Clouter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041019050616.GI19761@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=alex-kernel@digriz.org.uk \
    --cc=cpufreq@www.linux.org.uk \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®