mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Low bogomips on IBM x445 (kernel 2.6.5)
Date: Wed, 28 Apr 2004 13:36:53 -0700	[thread overview]
Message-ID: <1083184612.9664.15.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <408E3D74.2090301@inf.tu-dresden.de>

On Tue, 2004-04-27 at 04:01, Christoph Pohl wrote:
> I'm currently configuring an IBM x445 box with 4 Xeon CPUs (3GHz) and 
> hyperthreading enabled. Everything seems to work fine since kernel 2.6.5 
> but I keep wondering about the *very low* Bogomips numbers. Here is what 
> I see in /proc/cpuinfo:
> 
> cpu MHz         : 2996.175
[snip]
> bogomips        : 193.53

This is expected. Since the IBM x440/x445 are NUMA systems, we cannot
use the TSC (cpu cycle counter) as a time source. Instead we use an off
chip performance counter which runs at 100Mhz. This then translates to a
bogoMIPS value of ~200. 


> I came accross two bugs that looked very similar. However, they were 
> filed agains 2.4.x and should have been fixed for 2.6.x:
> 
> http://www.ussg.iu.edu/hypermail/linux/kernel/0311.0/0329.html
> 
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115061

These posts are about an old bug in 2.4 that was related to the
performance counter time source on the x44x systems. However in those
cases, bogoMIPS would be mis-calculated to ~3, which caused problems.
This issue does not affect 2.6 or recent 2.4 kernels.

thanks
-john




  parent reply	other threads:[~2004-04-28 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 11:01 Christoph Pohl
2004-04-27 18:01 ` Jurriaan
2004-04-28  5:50   ` Christoph Pohl
2004-04-28 10:28     ` Jurriaan
2004-04-28 20:36 ` john stultz [this message]
2004-04-28 21:11   ` Chris Friesen
2004-04-28 21:33     ` john stultz

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=1083184612.9664.15.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=christoph.pohl@inf.tu-dresden.de \
    --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®