Intel's 45nm Patch Machinery Exposed 78
Roboticles writes "Tweakers.net paid a visit to Intel's laboratories in the California town of Folsom, the birthplace of the 45nm CPU. We spoke to lead architect Stephen Fisher about the development of the Penryn chip and the day the first A0 version arrived. We were shown the machinery used to test and patch the 45nm processor, which is currently being manufactured in Arizona for release next month."
Need a magnifying glass (Score:3, Funny)
Re: (Score:2, Funny)
Re: (Score:1)
Re: (Score:2)
TickTock (Score:4, Insightful)
Imagine if Microsoft did it? Maybe we wouldn't end up with things like ME or Vista
I wonder if there's a competitive spirit between the teams.
Re: (Score:2, Informative)
Unfortunately ME development was hindered by the "Ballmer Peak".. http://xkcd.com/323/ [xkcd.com]
As a side thought, how far does light travel between clocks at 7Ghz? I make it about 4cm..
Re:TickTock (Score:4, Interesting)
Re: (Score:1)
Scratch that. I hope they were eaten by seals.
Re: (Score:2)
Re: (Score:2)
Few businesses would dare double their research just to reduce their risks.
It's a matter of affordability, and Intel can afford to have two rival design teams working in parallel on the same project. While this strategy proves to be a hedge on a risky bet, it has its disadvantages. Firstly, the design team can tend to slack off as it realizes that failure will not mean the death of the company. Secondly, they end up competing with each other instead of the competition, which can lead to some unhealthy internal politics, and it DOES! Intel managed to rise above the internal backbi
Re:TickTock (Score:5, Insightful)
Think about it, you would see the overall design come out, then that same design would be released on an improved process(going from 90 to 65nm for example). The design would be the same, just an improved process that would allow for faster versions of that design.
AMD has done it as well to an extent, but the high-end processors in the K8 generation are still on 90nm while the lower-clocked chips are at 65nm. Intel has more resources, so can throw more resources at fab process improvements while keeping the same number of resources focused on the overall CPU design.
Now, there are some disadvantages to Intel's method of approaching CPU innovation, including not looking for other ways to improve system performance. Think about it, AMD was able to do well due to the integrated memory controller and HyperTransport with a much smaller amount of cache. Even with these elements, will Intel come out with anything really NEW that will improve overall system performance?
So, Intel may hold the lead in terms of performance, or the AMD K10 architecture may allow AMD to catch back up. Either of these are possibilities at this point, and AMD is also working on things like adding some GPU functionality to their processors(Fusion being the first example of this). Even if the GPU power on the CPU is limited in terms of performance, it may add to the graphics processing power of an add-in video card to give an edge in terms of performance. Sure, Intel may be the platform for those who run MS Office, but for those who want some graphics power, AMD may end up with a clear advantage.
Tick-Tock is just an Intel way of saying they will do the same thing they always have, just pushing out improvements faster. AMD is focused more on figuring out ways to do things better because they can't keep up in a straight MHz competition, or on a straight fab process competition.
Re: (Score:2)
Re: (Score:2)
Tick-Tock speeds the push toward the newer t
Re: (Score:2)
Ummm... didn't read the article, did you? Tick-Tock was created precisely to address the issue of more aggressive CPU innovation. One ADVANTAGE of Intel's method is CPU innovation. The Nehalem team can look at all sorts of crazy new innovations without wondering if it will fail on actual silicon. The Penryn team will let the Nehalem team know where the trouble
Re: (Score:1)
Re: (Score:3, Interesting)
Re: (Score:2, Insightful)
Yeah, it only conquered the world. :)
Re: (Score:2)
Re: (Score:2, Insightful)
In non-benchmarks, it's a win because it's a compression for executable code.
It's only a win if your execution is bottlenecked by instruction bus bandwidth. That only happens if you're thrashing your L1 instruction cache, and THAT only happens with horribly bloated software and/or horribly small L1 caches.
While it's a good compression of executable code, it's good compression of x86 code. Other ISAs manage to pack way more into their instructions in the first place. Plus, the random alignment of x86 instructions means that the pipeline is elongated by a couple of stages just to f
Re: (Score:2, Informative)
"But it doesn't matter that you have to use 8 instructions to perform the same thing other arch's do in 1 opcode, because the microcode is really, really, really fast!!1"
Actually, you have it backwards. The x86 can do a handful of RISC instructions with a single instruction. That instruction might take longer to execute, but since you get more done for that one instruction, you get better instruction cache locality.
If you would like to troll on the failings of x86, there are well documented options for you. You must earn your troll-fu, young grasshoppa.
Re: (Score:1)
Actually, you have it backwards. The x86 can do a handful of RISC instructions with a single instruction. That instruction might take longer to execute, but since you get more done for that one instruction, you get better instruction cache locality.
On all the x86 architectures I know, if you use any instruction which gets microcoded, you end up with a huge performance hit. You basically run single pipelined until the microcode ends. These days, both Intel and AMD datasheets highly recommend you use simple form instructions as much as possible.
Yes, there comes a point where instruction cache locality matters more than instructions per clock. Your average bloated GUI app would benefit more from optimise-for-size than optimise-for-speed, for example (
Re: (Score:2)
How many of them can natively run code written for the 16-bit variant of their line that was produced 30 years ago?
While most would claim that native 8086 and heck even 32-bit pmode support really isn't needed in the day and age of "long mode," dropping them would be a huge pain and at that point you might a
Re: (Score:2)
Instruction length is, of course, only one factor, and I am guessing a minor factor, considering memory bandwidth, data cache associativity, floating point performance, and performance and flexibility of VM management seem to be more serious problems with current x86 implementations.
Not that any of it is really on topic
Re: (Score:2)
Re: (Score:2)
And besides, there is no level playing field for comparison when that RISC core is so lame, anyway. The quality example of that being that 800MHz Alpha's used to wipe the floor with 2 GHz Pentium IV's on floating point.
Re: (Score:2)
Re: (Score:2)
wow, 2 ACs?! (Score:2, Funny)
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
Re: (Score:3, Funny)
Re: (Score:2)
Re: (Score:1)
Re: (Score:1)
An IPOD is 0.27in thick
0.27in/1 * 0.0254m/1in * 1nm/10^-9m = 0.006858 * 10^9 = 6.9*10^6nm = IPOD NANO
45nm/1 * 1IPOD NANO/6.9*10^6nm = 6.5*10^-6 IPOD NANOS
That would be:0.0000065 IPOD Nanos to the 45 nanometer chip technology
I knew those chemistry conversion factors would come in helpful some day!!!
new prison job (Score:2)
Intel's laboratories in the California town of Folsom, the birthplace of the 45nm CPU
So that's what they make those software CEO's do in prison after back-dating stock options...
No more making license plates I guess!
ObJohnnyCash (Score:2)
"I once overclocked a CPU / just to watch it die..."
Folsom Labs Blues (Score:2)
And I ain't seen this performance since the 90nm process.
I'm stuck in Folsom Labs, and the clocks keep running faster,
But that deadline keeps on coming, from that Santa Clara.
When I was just a junior, my mentor told me, "Look,
Always be a good engineer, don't ever push your clock"
But I overclocked a CPU just to watch it die.
When I heard that core blowing, I hung my head and cried.
I bet those folks at AMD in their fancy die package
Are probably overclocking 'til
Not license plates... (Score:1)
No Linux testing? (Score:2)
Re:No Linux testing? Keep looking.. (Score:3, Informative)
Just because one article or press release was light on details, doesn't mean that it didn't happen. Here is what you seek. Intel did mention testing on Linux and some other operating systems.
http://enthusiast.hardocp.com/article.html?art=MTI2OCwxLCxoZW50aHVzaWFzdA== [hardocp.com]
"During a press briefing earlier today, Intel stated that the very first 45nm processor was already up and running and used by the Intel validation team to successfully boot a te
Re: (Score:2)
Re: (Score:1)
heh (Score:2)
Postal Service (Score:1)
Get the clip and you'll understand why.
It's not the hardware... (Score:1)
Quite obviously a software problem. Now if they had used Linux...
Geographical correction (Score:2)
Maybe it looks close if your home is in the Netherlands, but not in actual fact. No one goes to Folsom for the lake or the snow skiing (water skiing is another story). Folsom is almost at sea level, Lake Tahoe is at 6220 something, and 120 miles away.
Re: (Score:1)
Re: (Score:1)
Tickled. (Score:1)
Honestly, while it's interesting to see how they are developing this chip, I am so much more interested to see how it's going to stack up to AMD's new chip in the works. Especially seeing as intel is running the 45nm and AMD is still developing on the 65nm. I'm wondering if AMD's product could actually give them the boost they need to jump out from the depths of the AM2 debacle.
Re: (Score:2)
Re: (Score:1)
Manufacturing in Arizona? (Score:2)
Re: (Score:3, Informative)
The one in question here, Fab 32, is located in Chandler, Arizona which is one
Re: (Score:1)
Virtually no wafer fabs are located in China, for several reasons. The labor needed for a fab is skilled labor, so China offers no real advantages there. There are also a lot of issues regarding the export of "high tech" stuff to China. Most wafer fabs are located [10stripe.com] in the US, Japan, Taiwan, or Singapore.
Intel is actually currently talking about [arstechnica.com] building a fab in China. In order to stay on the good side of US regulators, it would be an "old tech" 90 nm fab. They would use it to make more "mature" produ
Re: (Score:2)
There are a lot of wafer fabs in China. SMIC being the biggest company. The number is likely to increase.
nothing new (Score:2)
Re: (Score:2)
Scaling is not driven by lithography anymore. It is driven by material science advances. Intel introduced Hafnium based gate dielectrics in 45nm, which is an incredibly impressive feat given that they are 1-2 years beyond all other companies.
Scaling by lithography was in the 80ies and early 90ies.
Dear Intel and/or AMD (Score:2)
However my new PC is still slow as hell and it doesn't feel any faster than the old one.
Re: (Score:1)
Tejas (Score:1)