From: Jurriaan <thunder7@xs4all.nl>
To: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Low bogomips on IBM x445 (kernel 2.6.5)
Date: Tue, 27 Apr 2004 20:01:17 +0200 [thread overview]
Message-ID: <20040427180117.GA2150@middle.of.nowhere> (raw)
In-Reply-To: <408E3D74.2090301@inf.tu-dresden.de>
From: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>
Date: Tue, Apr 27, 2004 at 01:01:08PM +0200
> Hello,
>
> 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:
>
What does
cat /proc/mtrr
say and how much memory is in that thing?
Jurriaan
--
Is it a son? Is it a daughter? It's an Addams!
Addams Family II
Debian (Unstable) GNU/Linux 2.6.6-rc2-mm2 2x6062 bogomips 2.58 1.39
next prev parent reply other threads:[~2004-04-27 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 11:01 Low bogomips on IBM x445 (kernel 2.6.5) Christoph Pohl
2004-04-27 18:01 ` Jurriaan [this message]
2004-04-28 5:50 ` Christoph Pohl
2004-04-28 10:28 ` Jurriaan
2004-04-28 20:36 ` john stultz
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=20040427180117.GA2150@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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