From: Dave Jones <davej@redhat.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Lee Revell <rlrevell@joe-job.com>,
cpufreq <cpufreq@www.linux.org.uk>
Subject: Re: [PATCH] CPU frequency display in /proc/cpuinfo
Date: Mon, 5 Dec 2005 12:26:51 -0500 [thread overview]
Message-ID: <20051205172651.GC12664@redhat.com> (raw)
In-Reply-To: <439463C4.7040905@rtr.ca>
On Mon, Dec 05, 2005 at 10:59:00AM -0500, Mark Lord wrote:
> >I can't think of a single valid reason why a program would want
^^^^^^^
> >to know the MHz rating of a CPU.
>
> Humans like to know what their machines are doing.
humans != programs
> Simple as that: it's for the end-users, and the place they look
> for it is always /proc/cpuinfo (since that works on every platform
> and on kernels prior to the 2.[56].* series.
Sure, 'cat' is the only reason its there at all.
> Not useful as an accurate number for any programming algorithms,
> but it is used to satisfy human curiosity. A lot.
I think we're in agreement, aren't we? :)
Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Mark Lord <lkml@rtr.ca>
Cc: 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 12:26:51 -0500 [thread overview]
Message-ID: <20051205172651.GC12664@redhat.com> (raw)
In-Reply-To: <439463C4.7040905@rtr.ca>
On Mon, Dec 05, 2005 at 10:59:00AM -0500, Mark Lord wrote:
> >I can't think of a single valid reason why a program would want
^^^^^^^
> >to know the MHz rating of a CPU.
>
> Humans like to know what their machines are doing.
humans != programs
> Simple as that: it's for the end-users, and the place they look
> for it is always /proc/cpuinfo (since that works on every platform
> and on kernels prior to the 2.[56].* series.
Sure, 'cat' is the only reason its there at all.
> Not useful as an accurate number for any programming algorithms,
> but it is used to satisfy human curiosity. A lot.
I think we're in agreement, aren't we? :)
Dave
next prev parent reply other threads:[~2005-12-05 17:26 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
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 [this message]
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=20051205172651.GC12664@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=rlrevell@joe-job.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.