Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Upgrade from single to dual core CPU
Date: Wed, 25 Jan 2006 20:05:53
Message-Id: pan.2006.01.25.20.01.36.566193@cox.net
In Reply to: Re: [gentoo-amd64] Upgrade from single to dual core CPU by Sebastian Redl
1 Sebastian Redl posted <43D7D08D.5080902@×××××××××××.at>, excerpted below,
2 on Wed, 25 Jan 2006 20:25:01 +0100:
3
4 > Matthias Wolle wrote:
5 >
6 >>You are right! AMD licenced HT-Technology from Intel.
7 >>AMD Dual Core CPU's uses this to fake a HT-CPU.
8 >>
9 >>
10 > "Fake"? Hyperthreading is just a fancy word for what AMD's "Dual Core"
11 > describes much better: these CPUs have multiple cores, i.e. instruction
12 > handlers, that share the integer, floating point etc. units. The idea is
13 > that, since in a conventional CPU all but one of these units are idle at
14 > all times, multiple cores could make better use of the CPU.
15
16 No, "dual-core" is just that, two CPUs on the same chip. In AMD's
17 implementation, since AMD has the memory management unit (MMU) on-chip as
18 well, the two cores do share the same MMU. Intel uses legacy
19 front-side-bus, with a separate MMU, and doesn't have the core-to-core
20 hypertransport (that's an AMD technology) either, so their implementation
21 is almost exactly like two CPUs that happen to be on the same chip.
22
23 Hyperthreading is just as you described -- a way for two threads to share
24 the same physical single-set of instruction handlers. As I stated in an
25 earlier post that probably crossed in the mail with yours, Intel benefits
26 from hyperthreading due to their deeper pipelining, left over from when
27 they were still working to increase clock cycles at all costs. AMD
28 apparently saw the end of the clock cycle gravy train sooner than Intel
29 did, and put their engineering resources into other alternatives such as
30 true dual core and on-chip MMUs. As a result, while they typically run at
31 a lower GHz, they have a somewhat shallower instruction pipeline and other
32 otherwise somewhat more efficient with their cycles, so manage quite well
33 in actual performance even at a lower cycle count. As well, they don't
34 benefit nearly as much from hyperthreading, while suffering the same
35 negatives, so they don't use it, choosing instead to go with a more
36 efficient true dual core design.
37
38 --
39 Duncan - List replies preferred. No HTML msgs.
40 "Every nonfree program has a lord, a master --
41 and if you use the program, he is your master." Richard Stallman in
42 http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
43
44
45 --
46 gentoo-amd64@g.o mailing list