From: Arjan van de Ven <arjan@infradead.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
"solsTiCe d'Hiver" <solstice.dhiver@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6
Date: Wed, 11 Jun 2008 06:58:16 -0700 [thread overview]
Message-ID: <20080611065816.6cff290d@infradead.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0806111552090.20733@fbirervta.pbzchgretzou.qr>
On Wed, 11 Jun 2008 15:52:57 +0200 (CEST)
Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Wednesday 2008-06-11 15:36, Arjan van de Ven wrote:
> >> >> btw this is scary; the Mhz line in /proc/cpuinfo doesn't have
> >> >> much meaning really, so applications using it and depending on
> >> >> it is a rather big disaster ;-(
> >> >>
> >> >> Does anyone know why jackd wants to use this?
> >>
> >> It would be nice to have a /sys file where the CPU frequency is in,
> >
> >may I ask why? What would you do with it?
>
> Off the top off the head, just for reporting to the user. Desklets
> and stuff.
even then it doesn't mean much ;-(
> >CPU frequency is...
> >1) not something that is fixed; it changes all the time
> >2) not a good indication for performance; remember the 3.4Ghz
> >pentium4, a 2Ghz Core2Duo outperforms it
> >3) something which the cpu itself barely honors (the clock stops
> >during idle etc etc)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-06-11 13:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:52 solsTiCe d'Hiver
2008-06-10 20:13 ` Arjan van de Ven
2008-06-10 20:42 ` Kok, Auke
2008-06-11 12:42 ` Jan Engelhardt
2008-06-11 13:36 ` Arjan van de Ven
2008-06-11 13:52 ` Jan Engelhardt
2008-06-11 13:58 ` Arjan van de Ven [this message]
2008-06-11 14:14 ` linux-os (Dick Johnson)
2008-06-11 15:10 ` Peter Zijlstra
2008-06-11 15:36 ` Arjan van de Ven
2008-06-11 16:59 ` Mark Hounschell
2008-06-11 17:44 ` Arjan van de Ven
2008-06-11 17:54 ` Mark Hounschell
2008-06-11 20:29 ` Arjan van de Ven
2008-06-11 20:37 ` Mark Hounschell
2008-06-11 20:55 ` Arjan van de Ven
2008-06-11 20:59 ` Mark Hounschell
2008-06-11 20:58 ` Arjan van de Ven
2008-06-11 21:08 ` Mark Hounschell
2008-06-11 21:28 ` Arjan van de Ven
2008-06-11 21:39 ` Chris Friesen
2008-06-11 23:08 ` Andi Kleen
2008-06-11 16:08 ` Ray Lee
2008-06-11 16:32 ` Arjan van de Ven
2008-06-11 12:40 ` Jan Engelhardt
2008-06-11 14:15 ` solsTiCe d'Hiver
2008-06-11 14:36 ` Jan Engelhardt
2008-06-11 15:35 ` solsTiCe d'Hiver
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=20080611065816.6cff290d@infradead.org \
--to=arjan@infradead.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=solstice.dhiver@gmail.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
Powered by JetHome