Details of New Intel Dunnington and Nehalem Architectures Leaked
Daily Tech is reporting that details about Intel's new processor models were leaked over the weekend. Both the six core Dunnington and Nehalem architectures were featured in this leak. "Dunnington includes 16MB of L3 cache shared by all six processors. Each pair of cores can also access 3MB of local L2 cache. The end result is a design very similar to the AMD Barcelona quad-core processor; however, each Barcelona core contains 512KB L2 cache, whereas Dunnington cores share L2 cache in pairs. [...] Nehalem is everything Penryn is -- 45nm, SSE4, quad-core -- and then some. For starters, Intel will abandon the front-side bus model in favor of QuickPath Interconnect; a serial bus similar to HyperTransport."
The Wikipedia page on QuickPath is very lacking in the realm of details. Does anyone know how it stacks up against HyperTransport? One of the most mouth-watering proposed uses for HT3 that I've heard of was the possibility for an external HT3 bus on a machine which could be used to link together multiple physical machines into one giant NUMA beast.
;)
Imagine a Beowulf of those
Am I the only one who thinks that having 3 cores, 6 cores, 3MB and 12MB is weird? Where did all the multiples of three come from in the sea of powers or 2. Did we suddenly switch to trinary or something?
"Intel will abandon the front-side bus..."
I think I speak for us all when I say ABOUT FSCKING TIME!
I don't really know the situation surrounding the technology, but even if Intel could use it for free, they would lose a huge battle in the PR War. I can see it now, "Remember that interconnect AMD has been using for years now? Well our design has finally caught up with theirs enough to use it." Remember that to the masses, the non-slashdot crowd, they have no idea what the techno-jargon spouted by Intel marketing means.
Intel currently has the superior technology, this is because of superior fabrication capabilities, not because of a superior architecture, if I've been following this correctly over the last few years. The general public is oblivious to the fact that internally the AMD architecture is cleaner and more elegant, the only thing they have to go on is marketing. If Intel were to adopt HyperTransport, which IIRC is trademarked by AMD, that would be a huge step backwards for Intel marketing, which is just recovering now that the Core 2 architecture has put them back on top.
I'm sick of following my dreams. I'm just going to ask where they're goin' and hook up with 'em later.
For the cache, the matter is simple. If you can fit 12 MB, but not 16, then 12 is still better than 8. You build them in 3 units of 4 MB each, so no big deal.
I seem to remember Intel made some proof-of-concept 80-core chip a while ago. Close enough.
How are sites slashdotted when nobody reads TFAs?
You mean this little piece of chippery?
But there was also, The Tualatin, the last of the P3's. .
I'm sick of following my dreams. I'm just going to ask where they're goin' and hook up with 'em later.
Intel did have a hell of a time confusing people before the concrete samples were available as to whether it was the same thing as AMD's 64-bit. They avoided using any term AMD associated with it for a time, instead tossing around ia32e and em64t and bs like that. I know some projects even baked into plans how to cope with yet another processor architecture for lack of a commitment from Intel that their 64-bit x86 compatible stuff would be the same.
Intel's hand was effectively forced because they learned their lesson from Itanium, don't screw with an incumbent variation of your flagship instruction set. With AMD's lead they would've risked yet another Itanium fiasco, so they picked the safe path and tried to PR dance around the existence of AMD's 64-bit stuff.
Itanium was an odd path in the history of Intel proving they truly thought they alone dictated the course of x86 technology. It stands in stark contrast to the history of supporting legacy all the way back to the 8086 days.
In this case, it's not the end-user or software developers being impacted, just hardware implementors who already have to do whatever the processor architecture dictates. Despite that freedom, Intel's unable to offer something that isn't obviously similar to the competing offering since it just is such a damn good idea. AMD has led some revolutionary changes in x86 architecture, while Intel has been able to follow up with evolutionary advances, fabrication, and marketing to continue eating the more significant profit margin space.
XML is like violence. If it doesn't solve the problem, use more.