[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080611063639.5e1eea5b@infradead.org>
Date: Wed, 11 Jun 2008 06:36:39 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: "Kok, Auke" <auke-jan.h.kok@...el.com>,
solsTiCe d'Hiver <solstice.dhiver@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6
On Wed, 11 Jun 2008 14:42:40 +0200 (CEST)
Jan Engelhardt <jengelh@...ozas.de> wrote:
>
> On Tuesday 2008-06-10 22:42, Kok, Auke wrote:
> >>>
> >>> and it appears that /proc/cpuinfo lack the line
> >>> cpu MHz:
> >>
> >>
> >> 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?
If it says 100Mhz, what would you conclude? That you have a slow cpu?
Or that you have a really fast CPU that currently runs at a low
frequency because you're mostly idle and are saving power?
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)
Userland apps that use "cpu frequency" seem to be buggy to me, at
least I don't believe that they understand the complexities about what
this means, and I don't believe that the decisions they make based on
this will be made correctly.
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists