mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Chris Meadors <clubneon@hereintown.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Better performance with 2.6
Date: Tue, 2 Mar 2004 14:58:50 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403021455380.1605@chaos> (raw)
In-Reply-To: <1078257097.7380.31.camel@clubneon.priv.hereintown.net>

On Tue, 2 Mar 2004, Chris Meadors wrote:

> On Tue, 2004-03-02 at 14:10, Richard B. Johnson wrote:
>
> > Are you talking about BogoMips??  This is just how many twinkies
> > you can eat in a second with the current coding style in the
> > short timer counter. It has absolutely, positively, nothing to
> > do with "CPU capacity".
>
> He probably meant MHz.  But the same thing.  What difference does a
> tenth of a MHz matter?
>
> I do have a question about BogoMIPS.  I know they don't mean anything,
> but why on my Opteron system with two processors that read the same on
> the cpu MHz line, do my bogomips vary so much?
>
> processor       : 0
> cpu MHz         : 1393.980
> bogomips        : 2736.12
>
> processor       : 1
> cpu MHz         : 1393.980
> bogomips        : 3145.72
>

Because the loop-counter is called at different times, therefore
the cache has different stuff in it.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-03-02 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 12:18 albhaf
2004-03-02 18:40 ` Mike Fedyk
2004-03-02 22:31   ` Andrea Arcangeli
2004-03-02 19:51 ` Albert Hafvenstrom
2004-03-02 19:10   ` Richard B. Johnson
2004-03-02 19:51     ` Chris Meadors
2004-03-02 19:58       ` Richard B. Johnson [this message]
2004-03-02 22:10 ` Darren Williams
2004-03-02 23:46   ` Mike Fedyk

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=Pine.LNX.4.53.0403021455380.1605@chaos \
    --to=root@chaos.analogic.com \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@vger.kernel.org \
    /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®