From: Michael Concannon <mike@concannon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Bogomips on AMD X2 (was Re:)
Date: Wed, 21 Sep 2005 09:58:55 -0400 [thread overview]
Message-ID: <4331671F.7000006@concannon.net> (raw)
In-Reply-To: <OF73453AE5.CDE706CC-ON80257083.004ACF55-80257083.004B7A0F@telex.com>
Robert.Boermans@uk.telex.com wrote:
>On Wednesday 21 September 2005 16:20, Robert.Boermans@uk.telex.com wrote:
>
>
>>Hello,
>>
>>I noticed that the bogomips results for the two cores on my machine are
>>consistently not the same, the second one is always reported slightly
>>faster, it's a small difference and I saw the same in a posted dmesg
>>
>>
>from
>
>
>>somebody else on the list. Which made me wonder:
>>
>>
>
>I guess it's a cache warming effect. Please show the numbers.
>--
>vda
>
>Probably not, got this one from a web site, and on this one the first core
>seems to be faster (can't check my own machine it's off and at home and
>I'm at work.) The difference I get is similar, but always with the second
>one faster. It's the same when using cat on /proc/cpuinfo. Oh and I saw it
>on 2.6.11 and 2.6.12 as supplied with fedora core 4 myself.
>
>Calibrating delay using timer specific routine.. 4014.73 BogoMIPS
>(lpj=8029470)
>Mount-cache hash table entries: 512
>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>CPU: L2 Cache: 512K (64 bytes/line)
>CPU 0(2) -> Core 0
>Intel machine check architecture supported.
>Intel machine check reporting enabled on CPU#0.
>mtrr: v2.0 (20020519)
>Enabling fast FPU save and restore... done.
>Enabling unmasked SIMD FPU exception support... done.
>Checking 'hlt' instruction... OK.
>CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
>Booting processor 1/1 eip 2000
>Initializing CPU#1
>Calibrating delay using timer specific routine.. 4005.37 BogoMIPS
>(lpj=8010751)
>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
>CPU: L2 Cache: 512K (64 bytes/line)
>CPU 1(2) -> Core 1
>Intel machine check architecture supported.
>Intel machine check reporting enabled on CPU#1.
>CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02
>Total of 2 processors activated (8020.11 BogoMIPS).
>
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
opposite result here - 2nd one is faster (from /proc/cpuinfo):
processor : 0
vendor_id : AuthenticAMD
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
cpu MHz : 2211.337
bogomips : 4374.52
...
processor : 1
vendor_id : AuthenticAMD
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
cpu MHz : 2211.337
...
bogomips : 4407.29
prev parent reply other threads:[~2005-09-21 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 13:20 Robert.Boermans
2005-09-21 13:27 ` Denis Vlasenko
2005-09-21 13:44 ` Bogomips on AMD X2 (was Robert.Boermans
2005-09-21 13:53 ` Denis Vlasenko
2005-09-21 14:02 ` Robert.Boermans
2005-09-21 14:14 ` OT: " Clemens Koller
2005-09-21 13:58 ` Michael Concannon [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=4331671F.7000006@concannon.net \
--to=mike@concannon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.