From: Arjan van de Ven <arjanv@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org,
linux-acpi <linux-acpi@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Dominik Brodowski <linux@brodo.de>
Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Tue, 21 Oct 2003 10:38:53 +0200 [thread overview]
Message-ID: <1066725533.5237.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60077914@scsmsx403.sc.intel.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Tue, 2003-10-21 at 04:56, Pallipadi, Venkatesh wrote:
> Patch 3/3: New dynamic cpufreq driver (called
> DemandBasedSwitch driver), which periodically monitors CPU
> usage and changes the CPU frequency based on the demand.
it's all nice code and such, but I still wonder why this can't be done
by a userland policy daemon. The 2.6 kernel has the infrastructure to
give very detailed information to userspace (eg top etc) about idle
percentages...... I didn't see anything in this driver that couldn't be
done from userspace.
Note that I'm not totally against doing some of this in the kernel; I
can well see the point of say, detecting an IRQ overload and based on
that, go to max speed in the kernel because it's a situation where
userspace doesn't even run; but the patch as is doesn't do any such
advanced things...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 2:56 [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-21 8:38 ` Arjan van de Ven [this message]
2003-10-21 9:59 ` Mattia Dongili
2003-10-21 10:17 ` Wichert Akkerman
2003-10-21 10:52 ` Mattia Dongili
2003-10-21 15:36 ` Daniel Thor Kristjansson
2003-10-21 20:32 ` Dominik Brodowski
2003-10-22 15:48 ` Daniel Thor Kristjansson
2003-10-23 14:32 ` Pavel Machek
2003-10-24 18:22 ` Dominik Brodowski
2003-10-21 19:23 ` Carl Thompson
2003-10-21 20:37 ` Dominik Brodowski
2003-10-23 14:17 ` Pavel Machek
2003-10-23 20:47 ` Moore, Robert
2003-10-23 21:50 ` Nakajima, Jun
2003-10-24 18:38 ` Dominik Brodowski
2003-10-24 11:27 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-10-24 18:52 Pallipadi, Venkatesh
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=1066725533.5237.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=asit.k.mallick@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--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