All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Dave Jones <davej@redhat.com>, Lee Revell <rlrevell@joe-job.com>,
	Andi Kleen <ak@suse.de>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Andrew Morton <akpm@osdl.org>, cpufreq <cpufreq@www.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CPU frequency display in /proc/cpuinfo
Date: Mon, 5 Dec 2005 14:02:24 +0100	[thread overview]
Message-ID: <20051205130224.GC17993@harddisk-recovery.com> (raw)
In-Reply-To: <20051205011611.GA12664@redhat.com>

On Sun, Dec 04, 2005 at 08:16:11PM -0500, Dave Jones wrote:
> I can't think of a single valid reason why a program would want
> to know the MHz rating of a CPU. Given that it's a) approximate,
> b) subject to change due to power management, c) completely nonsensical
> across CPU vendors, and d) only one of many variables regarding CPU
> performance, any program that bases any decision on the values found
> by parsing that field of /proc/cpuinfo is utterly broken beyond belief.

If you want a userspace governor to change the CPU speed, you need to
export the value to userland. There are several papers showing[1] that
such speed scheduling should be done by power-aware applications which
need to tell the OS what speed they require to run to meet their
processing needs.

I agree that /proc/cpuinfo shouldn't be used (though it is a nice
interface for humans to read about the CPU speed), but the current
sysfs interface should do.


Erik

[1] See for example
http://www.pds.twi.tudelft.nl/~pouwelse/energy_priority_scheduling.ps.gz
http://www.pds.twi.tudelft.nl/~pouwelse/power_aware_video_decoding.ps

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2005-12-05 13:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 18:13 [PATCH] CPU frequency display in /proc/cpuinfo Venkatesh Pallipadi
2005-12-02 18:19 ` Andi Kleen
2005-12-02 18:43   ` Venkatesh Pallipadi
2005-12-04 16:43     ` Dominik Brodowski
2005-12-04 18:32       ` Andi Kleen
2005-12-04 19:49         ` Lee Revell
2005-12-04 19:49           ` Lee Revell
2005-12-04 20:13           ` Andi Kleen
2005-12-04 20:13             ` Andi Kleen
2005-12-04 21:01           ` Horst von Brand
2005-12-05  1:16           ` Dave Jones
2005-12-05  1:16             ` Dave Jones
2005-12-05 13:02             ` Erik Mouw [this message]
2005-12-05 17:25               ` Dave Jones
2005-12-05 17:25                 ` Dave Jones
2005-12-05 17:27                 ` Lee Revell
2005-12-05 17:27                   ` Lee Revell
2005-12-06 11:13                 ` Erik Mouw
2005-12-06 16:56                   ` Dave Jones
2005-12-06 16:56                     ` Dave Jones
2005-12-06 17:35                     ` Erik Mouw
2005-12-05 15:32             ` Lee Revell
2005-12-05 15:32               ` Lee Revell
2005-12-05 18:36               ` Andi Kleen
2005-12-05 15:59             ` Mark Lord
2005-12-05 17:26               ` Dave Jones
2005-12-05 17:26                 ` Dave Jones
2005-12-05 16:29             ` Avi Kivity
2005-12-05 16:29               ` Avi Kivity
2005-12-05 16:46               ` linux-os (Dick Johnson)
2005-12-05 16:46                 ` linux-os (Dick Johnson)
2005-12-05 17:27               ` Dave Jones
2005-12-05 17:27                 ` Dave Jones

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=20051205130224.GC17993@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.