mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Jan Engelhardt" <jengelh@medozas.de>,
	"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 09:08:40 -0700	[thread overview]
Message-ID: <2c0942db0806110908i7d99b47ej155ae11d6d832077@mail.gmail.com> (raw)
In-Reply-To: <20080611063639.5e1eea5b@infradead.org>

On Wed, Jun 11, 2008 at 6:36 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> CPU frequency is...
> 1) not something that is fixed; it changes all the time

Not necessarily true of setups where jackd is running.

> 2) not a good indication for performance; remember the 3.4Ghz pentium4,
> a 2Ghz Core2Duo outperforms it

Your point only holds if jackd is somehow using this to compare
performance across different cpus. It's not.

> 3) something which the cpu itself barely honors (the clock stops during
> idle etc etc)

Again, that won't be happening when jackd is running.

> 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,

It doesn't appear you understand what jackd is and what lengths users
will go to to configure their systems for running it smoothly and
reliably.

> and I don't believe that the decisions they make based on
> this will be made correctly.

Please go read the jackd designs slides from the 2003 presentation on
the jack website [1]. The author has a clue, and is quite aware of how
computers work.

   [1] http://lad.linuxaudio.org/events/2003_zkm/slides/paul_davis-jack/title.html

  parent reply	other threads:[~2008-06-11 16:08 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
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 [this message]
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=2c0942db0806110908i7d99b47ej155ae11d6d832077@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=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

all inboxes | Powered by JetHome®