Skip to content

Biting the hand that feeds IT

The Register ®

Hardware:


Related Whitepapers

Comments on ‘Intel 'Nehalem' CPU 'borrows' AMD Phenom cache plan’

L3 promoted, L2 demoted

Published Monday 17th March 2008 19:02 GMT

« Back to article page

Doesnt that figure... 

By Walter Brown
Posted Tuesday 18th March 2008 01:55 GMT
Flame

Not only does Intel play the role of abusive monopolist (which is about the only thing its truly good at), they're stealing their idea's too...

I would love to Intel get broken up for violating its market position...

Cheater 

By Veil Sary
Posted Tuesday 18th March 2008 06:13 GMT

If Intel claimed that they make the best processor, why do they have to borrow AMD cache plan for? Why don't they create their own architecture than using other architecture?And let see how well will they stand against the 45 Quad Shanghai, Deneb, Montreal, Suzuki, Bulldozer, and Sandtiger.

Borrowed? 

By Ken Hagan
Posted Tuesday 18th March 2008 09:53 GMT
Unhappy

If I buy one of these chips, what happens when Intel give the cache layout back?

Seriously, I would have thought that cache sizes and connectivity were pretty much determined by the speed of the cores, the plumbing joining them to the outside world, and the assumptions about typical workload. I also expect we've seen similar plans in the mainframe and RISC world. To accuse Intel of borrowing AMD's plan is a bit like accusing bats of pinching the idea of wings from the birds, oblivious to the fact that insects got there first.

I'm not saying Nehalem's design isn't newsworthy, but I do question the choice of language.

Re: Borrowed 

By mike
Posted Tuesday 18th March 2008 11:42 GMT
Linux

"To accuse Intel of borrowing AMD's plan is a bit like accusing bats of pinching the idea of wings from the birds, oblivious to the fact that insects got there first."

Thankfully the insects didn't have the foresight to patent their wings ;)

borrowed... really? 

By Edison Asuncion Jr.
Posted Wednesday 19th March 2008 06:27 GMT
Alert

L3 shared cache is old intel server technology adopted by the K10m architecture (Phenom and Barcelona). so did intel really borrowed this from AMD?

borrowed/copied... here are some facts;

1. The use of a true 128-bit internal datapath. On previous CPUs based on K8 microarchitecture the internal datapath was of 64 bits only. This was a problem for SSE instructions, since SSE registers, called XMM, are 128-bit long. So, when executing an instruction that manipulated a 128-bit data, this operation had to be broke down into two 64-bit operations. The new 128-bit data path makes K10 microarchitecture faster to process SSE instructions that manipulate 128-bit data compared to K8 microarchitecture.

Intel processors based on Core microarchitecture (Core 2 Duo, for example) also have 128-bit internal datapaths , while Intel processors based on Netburst microarchitecture (Pentium 4 and Pentium D) have a 64-bit internal datapaths.

AMD is calling this new feature “AMD Wide Floating Point Accelerator”.

2. The fetch unit fetches 32 bytes (256 bits) of data per clock cycle from the L1 instruction cache – this is the double CPUs based on K8 architecture could fetch per clock cycle. Intel CPUs based on Core microarchitecture, like Core 2 Duo, also fetches 32 bytes per clock cycle.

3. K10 architecture adds a shared L3 memory cache (OLD INTEL SERVER CHIP TECHNOLOGY) inside the CPU... The size of this cache will depend on the CPU model, just like what happens with the size of L2 cache.

AMD calls this approach as “Balanced Smart Cache”.

http://ocxt.multiply.com/journal/item/47/Inside_AMD_K10_Architecture.

both sides getting the good ideas from each other. 

By Edison Asuncion Jr.
Posted Wednesday 19th March 2008 10:05 GMT
Happy

to make things short:

1. AMD Phenom (and Barcelona) copied Intel Core 2 Duo's true 128-bit internal datapath.

2. AMD Phenom (and Barcelona) copied Intel Core 2 Duo's Fetch Cycle - 32 bytes (256 bits) of data per clock cycle.

3. L3 Shared Cache is old Intel server technology adopted by Phenom and Barcelona.

--

both sides getting the good ideas from each other.

--

now with Intel Nehalem:

1. adopted integrated memory controller concept.

2. made a hypertransport-like bus and calls it Quick-Path Interconnect.

3. native/true quad/octo-core.

whitepaper title

Making Green IT a Reality

Customer Perspectives on the Impact of Storage Vendor Decisions on Power, Cooling, & Space in Enterprise Data Centers.
whitepaper title

Enabling the Data Center Metamorphosis

This independent analyst paper gives real world advice on transforming your datacenter into a streamlined, dynamic, liquid engine capable of handling growth..

Top 20 storiesAll The Week’s HeadlinesArchiveSearch