From: Bauke Jan Douma <bjdouma@xs4all.nl>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bogomips discrepancy on Intel Core2 Quad CPU
Date: Sun, 09 Sep 2007 01:03:57 +0200 [thread overview]
Message-ID: <46E32A5D.7080009@xs4all.nl> (raw)
In-Reply-To: <46DC1E9B.3030108@tmr.com>
Bill Davidsen wrote on 03-09-07 16:47:
> Bauke Jan Douma wrote:
>> $> uname -a
>> Linux skyscraper 2.6.22.5 #7 SMP PREEMPT Sun Sep 2 12:12:25 CEST 2007
>> i686 GNU/Linux
>>
>> $> cat /proc/cpuinfo | grep bogomips
>> bogomips : 4813.46
>> bogomips : 4810.91
>> bogomips : 4810.91
>> bogomips : 10583.94
>>
>> The latter seems way off base.
>> Prod me for more info.
>>
> I see this occasionally on a dual, speedstep (or similar) finds a way to
> throttle down the cores under light load. I suspect that if you load the
> system:
>
> for n in 1 2 3 4; do
> nice -19 bash -c 'while true; do a=$RANDOM; done' &
> done
>
> Then you should see your bogomips rise on all cores.
Sorry for now getting back on this sooner. Other matters forced it to
the backburner.
I don't have Speedstep enabled on this machine's kernel (as a matter
of fact, the entire cpufreq Kconfig subtree is unchecked). Needless to
say running your bash script doesn't change the values in any way.
I'd say the 4800-something bogomips value is the correct one (for a
2.4GHz CPU -- at least that's what I recall on single-CPU machines,
mostly bogomips being approx. twice the rated CPU speed), and the
10000-something is the one off base.
Btw., the 10000 can be something like 12000-odd after a machine reboot,
and readout on a different CPU. The rest are all ca. 4810. Odd indeed.
bjd
prev parent reply other threads:[~2007-09-08 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 8:06 Bauke Jan Douma
2007-09-03 14:47 ` Bill Davidsen
2007-09-03 15:44 ` Justin Piszcz
2007-09-08 23:03 ` Bauke Jan Douma [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=46E32A5D.7080009@xs4all.nl \
--to=bjdouma@xs4all.nl \
--cc=davidsen@tmr.com \
--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®