From: john stultz <johnstul@us.ibm.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Low bogomips on IBM x445 (kernel 2.6.5)
Date: Wed, 28 Apr 2004 14:33:14 -0700 [thread overview]
Message-ID: <1083187994.9664.24.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <40901E1A.9020904@nortelnetworks.com>
On Wed, 2004-04-28 at 14:11, Chris Friesen wrote:
> john stultz wrote:
>
> > 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.
>
> That sounds very strange. Bogomips is supposed to be how many busy-wait loops the cpu can do in a
> second, or at least that's what I've seen in all the books. It shouldn't matter what the time
> source is.
Well, sort of. bogoMIPS is derived from loops_per_jiffy, which when
using the PIT as a time source is how many busy-wait loops occur in a
timer tick. However when using the TSC as a timesource, the __delay()
function busy waits for a number of cycles. This increases the accuracy,
as interrupts taken do not affect the delay time. So in this case
bogoMIPS becomes the number of cpu cycles per tick. When using the
cyclone time source (the off chip performance counter) on the x440, it
becomes the number of cyclone cycles per tick.
thanks
-john
prev parent reply other threads:[~2004-04-28 21:34 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
2004-04-28 21:11 ` Chris Friesen
2004-04-28 21:33 ` john stultz [this message]
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=1083187994.9664.24.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=cfriesen@nortelnetworks.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®