Wow. Those are big dies.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Keysplayr

Elite Member
Jan 16, 2003
21,211
50
91
Originally posted by: zephyrprime
I wonder if there will be tri-core products since the defect rate is expected to be high? I don't think the cost will be as big a problem as many of you think because business will be buying these and they often budgets that are on a different scale than what we're used to. Businesses buy entire servers, not individual processors so the big cost of these processor is diluted by the rest of the hardware. And the cost of a 8-core machine with two chips may be less than the cost of a 8-core with 4 chips.


Is it technically possible to use 3 cores? I mean, I have never seen an odd number of CPU's in a system except for single of course. Always 2, 4, 8, 16, always doubling. 3 seems like it never happened for a reason. And I don't think it will ever happen.
 

CTho9305

Elite Member
Jul 26, 2000
9,214
1
81
Originally posted by: keysplayr2003
Originally posted by: zephyrprime
I wonder if there will be tri-core products since the defect rate is expected to be high? I don't think the cost will be as big a problem as many of you think because business will be buying these and they often budgets that are on a different scale than what we're used to. Businesses buy entire servers, not individual processors so the big cost of these processor is diluted by the rest of the hardware. And the cost of a 8-core machine with two chips may be less than the cost of a 8-core with 4 chips.


Is it technically possible to use 3 cores? I mean, I have never seen an odd number of CPU's in a system except for single of course. Always 2, 4, 8, 16, always doubling. 3 seems like it never happened for a reason. And I don't think it will ever happen.

1) The Xbox 360 CPU has 3 cores.
2) I've seen flaky Intel Xeon boxes report 3 processors in the OS (two single-core hyper-threaded CPUs)... the computer worked fine, and Linux scheduled only 3 threads to run, which I guess makes sense.
 

Keysplayr

Elite Member
Jan 16, 2003
21,211
50
91
Originally posted by: CTho9305
Originally posted by: keysplayr2003
Originally posted by: zephyrprime
I wonder if there will be tri-core products since the defect rate is expected to be high? I don't think the cost will be as big a problem as many of you think because business will be buying these and they often budgets that are on a different scale than what we're used to. Businesses buy entire servers, not individual processors so the big cost of these processor is diluted by the rest of the hardware. And the cost of a 8-core machine with two chips may be less than the cost of a 8-core with 4 chips.


Is it technically possible to use 3 cores? I mean, I have never seen an odd number of CPU's in a system except for single of course. Always 2, 4, 8, 16, always doubling. 3 seems like it never happened for a reason. And I don't think it will ever happen.

1) The Xbox 360 CPU has 3 cores.
2) I've seen flaky Intel Xeon boxes report 3 processors in the OS (two single-core hyper-threaded CPUs)... the computer worked fine, and Linux scheduled only 3 threads to run, which I guess makes sense.

1)That is a gaming console specifically made for gaming. I'm talking personal computers/servers.

2) Flaky really doesn't say much. In point, that system was designed for two processors (and hyperthreading running would make it two physical and two logical). My question is, why were PC's designed to run 1, 2, 4, 8, 16, 32 >infinity instead of 1,2,3, 4, 5, 6, 7, >infinity?

Much like everything else in the semiconductor industry, everything doubles for a reason. 1 bit, 2bit, 4bit, 8 bit, 16bit, 32 bit etc.

1MB, 2MB 4MB 8MB 16MB 32MB 64MB etc.

Also FSB speeds are a little confusing. Always increasing in 33MHz or 66MHz steps. 33, 66, 100, 133, 200 etc.

 

hans007

Lifer
Feb 1, 2000
20,212
18
81
Originally posted by: myocardia
Originally posted by: hans007
300mm^2 is giant. a conroe die is something like 140 mm for a 4mb one.

the amd cpu is supposed to be 4 x 512k cache,+ a shared 2mb cache. the ddr2 controller alone added an additionaly 20mm^2 on the am2 chips (in addition to whatever the ddr1 controller took) @ 90nm as well.

but 300mm^2 is gonna yield pretty badly especially with that many transistors. its made on the same process as the cell chip 65nm whcih is having awful yields (cell is a pretty large chip too) so it will be interesting to see how it works out.
This post makes absolutely no sense, hans. You're guessing that the AMD quad will be ~300mm², which you say is way too big, but then say that a Conroe die is 140mm². Isn't 140x2=280mm² pretty close to ~300mm² in your book, like it is in mine?

yeah but a 140 mm^2 conroe die, has a much lower chance of failure than a single 300 mm^2 die. say intel makes 2 conroe dies. if one fails, they can just make another one or turn the bad one into a core solo, or turn it into a dual core cpu. for intel its more l


amd wont be able to do that with the 4mb l3 cache and all that.
 

zephyrprime

Diamond Member
Feb 18, 2001
7,512
2
81
Originally posted by: keysplayr2003
1)That is a gaming console specifically made for gaming. I'm talking personal computers/servers.
It's not like 3 cores is naturally intrinsic to gaming consoles while being wholy unnatural in computers. Of course it's technically possible but it's probably inconvient or not efficient.

Actually, I doubt that there will be tri-core processors also. The defective quad coress will probably be sold as dual core procs.

 

myocardia

Diamond Member
Jun 21, 2003
9,291
30
91
Originally posted by: zephyrprime
It's not like 3 cores is naturally intrinsic to gaming consoles while being wholy unnatural in computers. Of course it's technically possible but it's probably inconvient or not efficient.

Actually, I doubt that there will be tri-core processors also. The defective quad coress will probably be sold as dual core procs.
Now that I think about it, I'm sure that it's just like 16, 24, and 32-bit color (with video cards). 24-bit was possible, but it was harder to do, and just as slow as 32-bit, which is why they ended up dropping it. I'm sure we'll just be seeing some extra large dual-cores, probably with 2MB of L3 cache, which should make it worthwhile for any bargain hunter, I would think.
 

lopri

Elite Member
Jul 27, 2002
13,310
687
126
I thought there was a consensus with more than 1 die -> x dice? (where x is the number)
 

Furen

Golden Member
Oct 21, 2004
1,567
0
0
Originally posted by: lopri
I thought there was a consensus with more than 1 die -> x dice? (where x is the number)

I dont think it makes a difference what people call them as long as they get their point across.

About the die-size. The shrink from 90nm to 65nm, like the shift from 130nm to 90nm and the ones before it, should yield close to a 50% die-size reduction (not everything in a die can be shrunk so much, of course). If you follow this logic then a quad-core K8 would indeed be a ~150mm^2 part because that's around what current dual-core X2s are. That said, either AMD added a whole lot of crap to "K8L" or this wafer is an earlier run that was not die-size optimized. I'd be inclined to say that the truth lies somewhere in the middle, that this is likely an earlier run (with test logic and the like) and K8L has many more transistors than regular K8s (which is a given considering all the improvements we've been hearing about).

AMD dislikes big die sizes because it is so capacity-constrained (it, in fact, considers even 1MBx2 CPUs too big and those are 200-220mm^2). That said, I'll say that I'm kind of looking forward for the ~90mm^2 65nm X2s that should be coming out relatively soon, since they'll allow AMD to drop the prices on the X2 line even further, which will also put a bit of a fire under Intel, though on the low-end.
 

coldpower27

Golden Member
Jul 18, 2004
1,676
0
76
Originally posted by: Furen
Originally posted by: lopri
I thought there was a consensus with more than 1 die -> x dice? (where x is the number)

I dont think it makes a difference what people call them as long as they get their point across.

About the die-size. The shrink from 90nm to 65nm, like the shift from 130nm to 90nm and the ones before it, should yield close to a 50% die-size reduction (not everything in a die can be shrunk so much, of course). If you follow this logic then a quad-core K8 would indeed be a ~150mm^2 part because that's around what current dual-core X2s are. That said, either AMD added a whole lot of crap to "K8L" or this wafer is an earlier run that was not die-size optimized. I'd be inclined to say that the truth lies somewhere in the middle, that this is likely an earlier run (with test logic and the like) and K8L has many more transistors than regular K8s (which is a given considering all the improvements we've been hearing about).

AMD dislikes big die sizes because it is so capacity-constrained (it, in fact, considers even 1MBx2 CPUs too big and those are 200-220mm^2). That said, I'll say that I'm kind of looking forward for the ~90mm^2 65nm X2s that should be coming out relatively soon, since they'll allow AMD to drop the prices on the X2 line even further, which will also put a bit of a fire under Intel, though on the low-end.

Dual Core K8 is now 183mm2 on the AM2 platform, so it's not as small anymore. As well you have got to factor in that K8L Quad Cores are supposed to come with 4x the cache available on the Dual Core Windsor. So the close to 300mm2 die figure hold some merit. As well an optical shrink with a processor typically doesn't yield 50% reduction on the whole, it's closer to 60% really given past die shrinks as a guide.

So K8L Quad Core will have something like 4x512kB plus the additional 2MB of LV3 cache.

If cache takes about 40mm2 for about 1MB of it on the 90nm node, since the cache area was about 80mm2 for the 2x1MB on Windsor, then on the 65nm node 40mm2 should account for the 2MB of LV3, so your looking at about 260mm2 then you have to add in K8L's additional complexity and close to 300mm2 will be around right.

Remember this is a Quad Core processor. 150mm2 is completely unrealistic even an optical shrink of Windsor would only yield 110mm2 with a 2x512KB die. Double that and you get the Quad Core at 220mm2. Now with that said 90mm2 is also too small for 65nm Dual Core, Brisbane if it's 2x512KB only will be around the size that San Diego was so 110mm2 or so which is very reasonable.

AMD doesn't have much choice, the first introduction of a new architecture tends to be a large die given the past.

K7 Pluto on 0.25 micron 184mm2
K8 Clawhammer on 0.13 micron 193mm2
K8 Toledo Dual Core on 90 nm 199mm2

And 300mm2 would be in line considering that AMD has the use of 300mm wafers now and the processor listed above were built with 200mm wafers as a starting point.

This is one of the nice things about Intel's approach, they can use any 2x143mm2 dies on the wafer or 2 different wafers entirely to build their Kentsfield based processor.
 

Furen

Golden Member
Oct 21, 2004
1,567
0
0
Originally posted by: coldpower27

Dual Core K8 is now 183mm2 on the AM2 platform, so it's not as small anymore. As well you have got to factor in that K8L Quad Cores are supposed to come with 4x the cache available on the Dual Core Windsor. So the close to 300mm2 die figure hold some merit. As well an optical shrink with a processor typically doesn't yield 50% reduction on the whole, it's closer to 60% really given past die shrinks as a guide.

So K8L Quad Core will have something like 4x512kB plus the additional 2MB of LV3 cache.

If cache takes about 40mm2 for about 1MB of it on the 90nm node, since the cache area was about 80mm2 for the 2x1MB on Windsor, then on the 65nm node 40mm2 should account for the 2MB of LV3, so your looking at about 260mm2 then you have to add in K8L's additional complexity and close to 300mm2 will be around right.

Remember this is a Quad Core processor. 150mm2 is completely unrealistic even an optical shrink of Windsor would only yield 110mm2 with a 2x512KB die. Double that and you get the Quad Core at 220mm2. Now with that said 90mm2 is also too small for 65nm Dual Core, Brisbane if it's 2x512KB only will be around the size that San Diego was so 110mm2 or so which is very reasonable.

Calm down, my friend, I was just doing a bit of brainstorming, not claiming that I know everything absolutely or anything of the sort (all those "shoulds" and the like should show that I'm purely speculating). I said 50% simply to make the calculations easier. I'll try again.

Let's say AMD decided to make a quad-core K8 (not K8L). First off, you only need a single northbridge and memory controller. If you think this is small just look at the increase in die-size that AM2 brought by adding DDR2 support and (according to the inq) quad crossbar ports, I'd guess (a wild guess) that the stuff that does not need to be duplicated is around 50mm^2 of the die, which would mean that around 130mm^2 would need to be duplicated. So 2x130=260 + 50 = 310mm^2. That would be the die size for quad-core K8 on the 90nm node. Assuming a 57% die-size due to the 65nm shrink (a winchester is about 57% the die size of a newcastle) that would give us a 177mm^2 die size. I'm probably low-balling it a bit since a lot of the info needed to calculate it is purely speculation but I'm probably not off by a whole lot. Consider that a Clawhammer (at 130nm) has a die size of 193mm^2 and a Toledo (dual-core, 90nm) has a die size of 199mm^2. Same cache sizes, and Toledo added SSE3.

So that leaves a whole lot of space for the L3 cache and the K8L improvements. I'm not gonna claim that our estimates are wrong (I, too, calculated around 300mm^2 for the die size of those monsters), I'm just saying that those dice may not be final quad-core silicon.

EDIT: By the way, when I said "90mm^2 X2s" I was talking about 65nm Manchesters, lol... stupid AM2 die-sizes always screw me over (I used 150mm^2 * .6 to calculate that), so you're right about that. AMD does indeed have more production capacity but it also serves a much bigger market. AMD pretty much said that it didn't want to produce 2x1MB L2 X2s 'cause they're too big and strain its capacity, even with FAB36 and Chartered fabbing for AMD. Clawhammer was indeed huge when it came out but the process was very mature and 90nm was coming relatively soon after its introduction, and a cache-cut part came out as well after a bit. Cache was a huge chunk of Clawhammer, I dont think it's going to be that big of a part of K8L.
 

coldpower27

Golden Member
Jul 18, 2004
1,676
0
76
Originally posted by: Furen
Originally posted by: coldpower27

Dual Core K8 is now 183mm2 on the AM2 platform, so it's not as small anymore. As well you have got to factor in that K8L Quad Cores are supposed to come with 4x the cache available on the Dual Core Windsor. So the close to 300mm2 die figure hold some merit. As well an optical shrink with a processor typically doesn't yield 50% reduction on the whole, it's closer to 60% really given past die shrinks as a guide.

So K8L Quad Core will have something like 4x512kB plus the additional 2MB of LV3 cache.

If cache takes about 40mm2 for about 1MB of it on the 90nm node, since the cache area was about 80mm2 for the 2x1MB on Windsor, then on the 65nm node 40mm2 should account for the 2MB of LV3, so your looking at about 260mm2 then you have to add in K8L's additional complexity and close to 300mm2 will be around right.

Remember this is a Quad Core processor. 150mm2 is completely unrealistic even an optical shrink of Windsor would only yield 110mm2 with a 2x512KB die. Double that and you get the Quad Core at 220mm2. Now with that said 90mm2 is also too small for 65nm Dual Core, Brisbane if it's 2x512KB only will be around the size that San Diego was so 110mm2 or so which is very reasonable.

Calm down, my friend, I was just doing a bit of brainstorming, not claiming that I know everything absolutely or anything of the sort (all those "shoulds" and the like should show that I'm purely speculating). I said 50% simply to make the calculations easier. I'll try again.

Let's say AMD decided to make a quad-core K8 (not K8L). First off, you only need a single northbridge and memory controller. If you think this is small just look at the increase in die-size that AM2 brought by adding DDR2 support and (according to the inq) quad crossbar ports, I'd guess (a wild guess) that the stuff that does not need to be duplicated is around 50mm^2 of the die, which would mean that around 130mm^2 would need to be duplicated. So 2x130=260 + 50 = 310mm^2. That would be the die size for quad-core K8 on the 90nm node. Assuming a 57% die-size due to the 65nm shrink (a winchester is about 57% the die size of a newcastle) that would give us a 177mm^2 die size. I'm probably low-balling it a bit since a lot of the info needed to calculate it is purely speculation but I'm probably not off by a whole lot. Consider that a Clawhammer (at 130nm) has a die size of 193mm^2 and a Toledo (dual-core, 90nm) has a die size of 199mm^2. Same cache sizes, and Toledo added SSE3.

So that leaves a whole lot of space for the L3 cache and the K8L improvements. I'm not gonna claim that our estimates are wrong (I, too, calculated around 300mm^2 for the die size of those monsters), I'm just saying that those dice may not be final quad-core silicon.

EDIT: By the way, when I said "90mm^2 X2s" I was talking about 65nm Manchesters, lol... stupid AM2 die-sizes always screw me over (I used 150mm^2 * .6 to calculate that), so you're right about that. AMD does indeed have more production capacity but it also serves a much bigger market. AMD pretty much said that it didn't want to produce 2x1MB L2 X2s 'cause they're too big and strain its capacity, even with FAB36 and Chartered fabbing for AMD. Clawhammer was indeed huge when it came out but the process was very mature and 90nm was coming relatively soon after its introduction, and a cache-cut part came out as well after a bit. Cache was a huge chunk of Clawhammer, I dont think it's going to be that big of a part of K8L.

Just wanted to make sure.

Heh, I doubt there is that much unneeded circuitry on the Dual Core K8, if the memory controller was boosted to serve 4 cores instead it would indeed become larger. 50mm2 of the die doesn't need to be duplicated out of 183mm2, I am not going to call you wrong, but I seriously doubt that much of the die is saved. And yes I did factor in the fact that it was a Dual Core K8 which you were talking about.

I really don't think the SSE3 instruction set is really a significant part of the die space. The San Diego core at 114mm2 already had that and Toledo was 199mm2, which is 58% the size of Toledo, so they saved 8% die space from Single to Dual Core, using that as a baseline.

I get about 190mm2 for a Quad Core K8 on the 65nm node or 316mm2 on the 90nm node. Which is mildly higher then what you have.

Well that is pretty obvious that AMD wants to optimize it's production capacity, they want to make as much money as they can, even with Fab 36 online, and the impending transistion of Fab 30 to Fab 38 and Fab 7 of Chartered Semi COnductor, as there is now rumors of the 0.5x multiplier 4000+, 4400+, 4800+ instead of having 2x1MB of cache, with the die size I predicted these cores with only 2x512KB cache now will be around the same level as Allendale. They will still prove to be more expensive in production cost then Allendale, due to the fact that AMD uses DSL SOI and that they are at least 1 layer thicker, but they are more optimal.

Soon is a matter of perspective I guess, Clawhammer came out in September 2003, and the 90nm shrink of that core didn't come till April 2005 for the desktop with San Diego, but like I said a core that intorduced a new architecture tends to be at least 200mm2 or close to it on the AMD side and this is using 200mm wafers, with 300mm wafers a ~300mm2 die size to start wouldn't be surprising. Though AMD does do a cache cut if they find they need more room to compete.

On the Intel side of the fence it varies.

Willamette on 0.18 micron is 217mm2 (Big)
Pentium M on 0.13 micron is 82.8mm2 (Small)
Core 2 Duo on 65nm is 143mm2 (Medium)

Yeah, but I would say we should stick with these die size estimates until more concrete proof comes along that can negate the picture we have seen here, 300mm2 is pretty damn realistic IMO. 65nm Quad Cores will be more expensive to produce relative to even 90nm Dual Cores, it will take hte 45nm process to bring this down to a more reasonable level.

Regarding the optical shrink I would say 60% is fair. Since the 0.13 micron to 0.09 micron shrink should yield a die size of 48% if mathematically perfect, so 58% is 10% larger, 90nm to 65nm is 52% for mathematically perfect, so 60% is fine for that.

No if Intel has 2x4MB and that is around 40% of the die for Core Architecture, then (4x512KB & 2MB) is not going to be that significant on K8L, maybe somewhere in the 30% range. But it will be enough to bring the die size to ~300mm2 or so, with the Quad Core K8L.

EDIT: Spelling, and minor additions.
 

Furen

Golden Member
Oct 21, 2004
1,567
0
0
Originally posted by: coldpower27
Just wanted to make sure.

Heh, I doubt there is that much unneeded circuitry on the Dual Core K8, if the memory controller was boosted to serve 4 cores instead it would indeed become larger. 50mm2 of the die doesn't need to be duplicated out of 183mm2, I am not going to call you wrong, but I seriously doubt that much of the die is saved. And yes I did factor in the fact that it was a Dual Core K8 which you were talking about.

I really don't think the SSE3 instruction set is really a significant part of the die space. The San Diego core at 114mm2 already had that and Toledo was 199mm2, which is 58% the size of Toledo, so they saved 8% die space from Single to Dual Core, using that as a baseline.

I get about 190mm2 for a Quad Core K8 on the 65nm node or 316mm2 on the 90nm node. Which is mildly higher then what you have.

Well that is pretty obvious that AMD wants to optimize it's production capacity, they want to make as much money as they can, even with Fab 36 online, and the impending transistion of Fab 30 to Fab 38 and Fab 7 of Chartered Semi COnductor, as there is now rumors of the 0.5x multiplier 4000+, 4400+, 4800+ instead of having 2x1MB of cache, with the die size I predicted these cores with only 2x512KB cache now will be around the same level as Allendale. They will still prove to be more expensive in production cost then Allendale, due to the fact that AMD uses DSL SOI and that they are at least 1 layer thicker, but they are more optimal.

Soon is a matter of perspective I guess, Clawhammer came out in September 2003, and the 90nm shrink of that core didn't come till April 2005 for the desktop with San Diego, but like I said a core that intorduced a new architecture tends to be at least 200mm2 or close to it on the AMD side and this is using 200mm wafers, with 300mm wafers a ~300mm2 die size to start wouldn't be surprising. Though AMD does do a cache cut if they find they need more room to compete.

On the Intel side of the fence it varies.

Willamette on 0.18 micron is 217mm2 (Big)
Pentium M on 0.13 micron is 82.8mm2 (Small)
Core 2 Duo on 65nm is 143mm2 (Medium)

Yeah, but I would say we should stick with these die size estimates until more concrete proof comes along that can negate the picture we have seen here, 300mm2 is pretty damn realistic IMO. 65nm Quad Cores will be more expensive to produce relative to even 90nm Dual Cores, it will take hte 45nm process to bring this down to a more reasonable level.

Regarding the optical shrink I would say 60% is fair. Since the 0.13 micron to 0.09 micron shrink should yield a die size of 48% if mathematically perfect, so 58% is 10% larger, 90nm to 65nm is 52% for mathematically perfect, so 60% is fine for that.

No if Intel has 2x4MB and that is around 40% of the die for Core Architecture, then (4x512KB & 2MB) is not going to be that significant on K8L, maybe somewhere in the 30% range. But it will be enough to bring the die size to ~300mm2 or so, with the Quad Core K8L.

EDIT: Spelling, and minor additions.

Heh, the difference in real die size between Toledo and San Diego is 85mm^2. That, we can assume, is the die size of a single core with its 1MB of cache. That means that with Toledo 170mm^2 is Execution cores + L2 and 29mm^2 is the SRI, Crossbar and Memory controller and we can also say that two 512K cores take around 126mm^2 or 63mm^2 per core. I'll accept that those Barcelona cores do indeed look to be around 300mm^2 but goddam, that's freaking huge considering that AMD is so capacity constrained. Although it indeed does have 300mm wafers, FAB36 does less wafer starts per month than FAB30 so the capacity increase is not necessarily linear. AMD is also barely about to start ramping up 65nm production so the 65nm wafer starts could be way less, not to mention that dual-core Rev Gs will also take a sizeable chunk out of that.

I'll say this, If AMD's final die-size for K8L is indeed 300mm^2 then maybe AMD would be better served making 4 core Rev G parts instead of introducing such a huge die. Not as sexy but the performance deficit compared to Core would lessen a bit in quad-core parts and they would be much cheaper to produce (I'm guessing a single 200mm^2 die is cheaper to produce and package than two 150mm^2 dice in an MCP). I know that AMD claims it won't be too far behind Intel in the introduction of 45nm but producing 300mm^2 monsters for a year (more, most likely) is not all that desirable. Quad-core could indeed be limited to the extreme high end, so the volumes may be low enough, but if Intel pushes its comparatively cheap Kentsfield into the mainstream AMD will be in trouble (again ).
 

coldpower27

Golden Member
Jul 18, 2004
1,676
0
76
Originally posted by: Furen
Heh, the difference in real die size between Toledo and San Diego is 85mm^2. That, we can assume, is the die size of a single core with its 1MB of cache. That means that with Toledo 170mm^2 is Execution cores + L2 and 29mm^2 is the SRI, Crossbar and Memory controller and we can also say that two 512K cores take around 126mm^2 or 63mm^2 per core. I'll accept that those Barcelona cores do indeed look to be around 300mm^2 but goddam, that's freaking huge considering that AMD is so capacity constrained. Although it indeed does have 300mm wafers, FAB36 does less wafer starts per month than FAB30 so the capacity increase is not necessarily linear. AMD is also barely about to start ramping up 65nm production so the 65nm wafer starts could be way less, not to mention that dual-core Rev Gs will also take a sizeable chunk out of that.

I'll say this, If AMD's final die-size for K8L is indeed 300mm^2 then maybe AMD would be better served making 4 core Rev G parts instead of introducing such a huge die. Not as sexy but the performance deficit compared to Core would lessen a bit in quad-core parts and they would be much cheaper to produce (I'm guessing a single 200mm^2 die is cheaper to produce and package than two 150mm^2 dice in an MCP). I know that AMD claims it won't be too far behind Intel in the introduction of 45nm but producing 300mm^2 monsters for a year (more, most likely) is not all that desirable. Quad-core could indeed be limited to the extreme high end, so the volumes may be low enough, but if Intel pushes its comparatively cheap Kentsfield into the mainstream AMD will be in trouble (again ).

Well they don't have a choice since they are hyping up their "native" parts. It is unknown whether or not a Quad Core Rev.G processor would be closer to the Kentsfield then Dual Core Rev.G will be in comparison to Conroe.

Hence why I am not convinced we are going to see anything but Socket F parts for Barcelona cores in the Q2 2007 launch. They are pretty large products, it would be smart for AMD to push them for Servers where the profits are highest and where they stand to get the most out of them.

Well it's currently unknown how far Intel will push Quad Core towards the mainstream, Who knows maybe later down the line we might get some Kentsfield designs based on Allendale instead of Conroe, pushing Quad Core further down. It's probably up to Intel how aggressive they want to be on this, I hope that Intel is agressive though cheaper Quad Core SKU's would be quite good for certain applications.

By the time these Barcelona cores roll around though I assume AMD will have a decent amount of 65nm capacity, with the continued ramp of Fab 36.

Not to mention this "native" advantage won't hold for long as in Q3 2007 Intel will be releasing Yorkfield which has a Shared Cache pool between all 4 Cores.

I think it would be in both AMD and Intel interest to take a break from increasing the no. of cores on the 45nm generation and simply leave it at 4 there and concentrate on refining other aspects other then "more cores" and resume perhaps the increase on the 32nm generation. Though a 8 Core processor for Servers, would be a good idea.
 

hans007

Lifer
Feb 1, 2000
20,212
18
81
actually the am2 x2 chips were 220 mm^2 for the 2 x 1mb cache version that they quickly discontinued . the difference between the 512x2 and 1mb x2 was 40mm ^2 or so.

the ddr2 controller added something like 25 mm ^2 over the 939 version.

with 4mb cache and 1 ddr2 controller instead of 2. i would assume it would be still a little over the size of 2 65nm dual cores. 4mb of cache will take a lot more space then 1 ddr2 controller (since it will only have 1 instead of 2). 300mm^2 i think its a good estimate.
 

Furen

Golden Member
Oct 21, 2004
1,567
0
0
Originally posted by: coldpower27
Well they don't have a choice since they are hyping up their "native" parts. It is unknown whether or not a Quad Core Rev.G processor would be closer to the Kentsfield then Dual Core Rev.G will be in comparison to Conroe.

[...]

By the time these Barcelona cores roll around though I assume AMD will have a decent amount of 65nm capacity, with the continued ramp of Fab 36.

Not to mention this "native" advantage won't hold for long as in Q3 2007 Intel will be releasing Yorkfield which has a Shared Cache pool between all 4 Cores.

I think it would be in both AMD and Intel interest to take a break from increasing the no. of cores on the 45nm generation and simply leave it at 4 there and concentrate on refining other aspects other then "more cores" and resume perhaps the increase on the 32nm generation. Though a 8 Core processor for Servers, would be a good idea.

A quad-core Rev G would still be native quad core, since all the interconnections would be done within the die thought the SRI. If AMD were able to pump out a 3.0GHz+ Rev G quad core then it'd have no problem matching Intel's Kentfield. Or getting close enough, anyway. AMD would still be something like 5-10% behind compared to a 2.67GHz Kentsfield but nothing too dramatic.

AMD will indeed have much more 65nm capacity by next year but will it have SPARE capacity?

I, too, think that there's no point to going over 4 cores in the mainstream. Hell, 4 cores may still be overkill. I think we're going to start getting some funky designs after we get 4 cores, perhaps microcores or perhaps integrated graphics in the CPU. I doubt Intel would be able to throw 8 cores in an MCP package, since the FSB will, once again, become a horrendous bottleneck.
 

coldpower27

Golden Member
Jul 18, 2004
1,676
0
76
Originally posted by: Furen
A quad-core Rev G would still be native quad core, since all the interconnections would be done within the die thought the SRI. If AMD were able to pump out a 3.0GHz+ Rev G quad core then it'd have no problem matching Intel's Kentfield. Or getting close enough, anyway. AMD would still be something like 5-10% behind compared to a 2.67GHz Kentsfield but nothing too dramatic.

AMD will indeed have much more 65nm capacity by next year but will it have SPARE capacity?

I, too, think that there's no point to going over 4 cores in the mainstream. Hell, 4 cores may still be overkill. I think we're going to start getting some funky designs after we get 4 cores, perhaps microcores or perhaps integrated graphics in the CPU. I doubt Intel would be able to throw 8 cores in an MCP package, since the FSB will, once again, become a horrendous bottleneck.

That the key word IF, as it doesn't look like AMD will reach 3.0GHZ on 65nm node, anytime soon. They would be lucky if by the time Q2 2007 rolls around they have 3.0GHZ Dual Core K8's let alone the theoretical Quad Core K8 which needs 3GHZ+ to be not behind too much the QX6700 Intel will be releasing this November.

Hard to say at this point. I am sure AMD will figure out how to best use the available 65nm capacity they have. For their sake I would hope Quad Core K8L's don't kill their production line when they start to produce them for revenue in Mid 2007. I don't think they will be too bad a shape even with Barcelona production however.

By the time we roll around to getting 8 Cores onto a Single Socket, I assume Intel will have moved onto the Nehalem based processors with CSI. So the FSB issue will be moot.

I look forward to seeing what the future will bring for both comapnies, as I expect them to tinker with their architectures again once 4 Cores is conquered and we have left over die area to spare.


 

Furen

Golden Member
Oct 21, 2004
1,567
0
0
Perhaps 3.0GHz is indeed too high for the initil 65nm parts but we won't know how fast these clocks will ramp up. The fact that AMD has a 3GHz part coming out next month (hey, it's already October, lol) might mean there's hope for the 65nm parts, after all, they'll all have a 65W TDP. Of course, AMD is not working on a quad-core Rev G so this speculation is moot.

I meant that dual-die non-native octal-core is not doable on a FSB architecture, heck I doubt even single-die octal-core is doable unless FSB speed increase massively. I wonder if Intel will continue doing dual-die chips even after CSI debuts. Having two memory controllers and two northbridges (one on each core) seems kind of wasteful, part of the reason why AMD doesn't do dual-die stuff, IMO (the other part being that it can't fit two damn dies under the IHS, lol).
 

coldpower27

Golden Member
Jul 18, 2004
1,676
0
76
Originally posted by: Furen
Perhaps 3.0GHz is indeed too high for the initil 65nm parts but we won't know how fast these clocks will ramp up. The fact that AMD has a 3GHz part coming out next month (hey, it's already October, lol) might mean there's hope for the 65nm parts, after all, they'll all have a 65W TDP. Of course, AMD is not working on a quad-core Rev G so this speculation is moot.

I meant that dual-die non-native octal-core is not doable on a FSB architecture, heck I doubt even single-die octal-core is doable unless FSB speed increase massively. I wonder if Intel will continue doing dual-die chips even after CSI debuts. Having two memory controllers and two northbridges (one on each core) seems kind of wasteful, part of the reason why AMD doesn't do dual-die stuff, IMO (the other part being that it can't fit two damn dies under the IHS, lol).

Well the 5000+ on 65nm has a TDP of 76W according to the latest roadmaps, so we will have to see. Though it still looks like the 65nm transistion will be Winchester like at first, with the mianstream SKU's.

I don't know about that, Core Architecture doesn't seem that bandwidth constrained. If the FSB was increased to 1.33GHZ you would have 166MHZ of Bandwidth per Core if you had an Dual Die Octal Core processor. There isn't any indication at all that Core is bandwidth constrained. We will have to see when CSI debuts before we find out that. Dual Die isn't the most efficient so to say, but it is the way that is less work as your taking 2 existing processor and just putting it on the same package. But like I said, Octal Core is unlikely to be debuting on COre Arhcitecture and will likely start with Nehalem based products.

 

hans007

Lifer
Feb 1, 2000
20,212
18
81
amd, is starting to lose the fab race because of the delays with the ibm process. by the time they really have 65nm going ta the same speed as their 90nm parts in mid 2007 intel will have started their 45nm process which is slated for 2h 2007 .

the first gen 65nm is supposed to only be up to 2.6ghz which is the 5000+. i'd assume they could eventually get it to 3.0ghz, but speed increases per process have not really been there for a while for either company. its just smaller dies / less power. and at 45nm intel will probaby be quite ahead on the power front.

a 2.6 quad core 65nm amd chip with a monolithic die will probably use 150watts (if the 5000+ is really 76 watts tdp) or more because of the 4mb cache.

seeing as a 2.67 ghz intel quad core is only using 125watts now and is faster its gonna be a tough battle unless amd pulls something out of their ass since that theoretical quadcore monolithic die 2.6hz amd chip will cost an assload to produce compared to even a kentsfield 2.67 since the kentsfields are split onto 2 cores which are 143 mm each. iwould like to honestly see a dual allendale core. 2 112mm^2 dies, say 2.13ghz $350. i'd buy that. c'mon intel give it to us.

 

BrownTown

Diamond Member
Dec 1, 2005
5,314
1
0
because the silicon ingots are cylinders, and when you get them in pieces you get circles.
 

CTho9305

Elite Member
Jul 26, 2000
9,214
1
81
because the silicon ingots are cylinders, and when you get them in pieces you get circles.
And since the next question to come up will probably "why are they round"... wafers are produced by spinning a crystal seed slowly in molten silicon, which slowly cools. As it solidifies, it solidifies into a single crystal grown on that seed. They need to be a single crystal - grain boundaries (the border between crystals) are defects. The rotation makes it a cylinder.
 
sale-70-410-exam    | Exam-200-125-pdf    | we-sale-70-410-exam    | hot-sale-70-410-exam    | Latest-exam-700-603-Dumps    | Dumps-98-363-exams-date    | Certs-200-125-date    | Dumps-300-075-exams-date    | hot-sale-book-C8010-726-book    | Hot-Sale-200-310-Exam    | Exam-Description-200-310-dumps?    | hot-sale-book-200-125-book    | Latest-Updated-300-209-Exam    | Dumps-210-260-exams-date    | Download-200-125-Exam-PDF    | Exam-Description-300-101-dumps    | Certs-300-101-date    | Hot-Sale-300-075-Exam    | Latest-exam-200-125-Dumps    | Exam-Description-200-125-dumps    | Latest-Updated-300-075-Exam    | hot-sale-book-210-260-book    | Dumps-200-901-exams-date    | Certs-200-901-date    | Latest-exam-1Z0-062-Dumps    | Hot-Sale-1Z0-062-Exam    | Certs-CSSLP-date    | 100%-Pass-70-383-Exams    | Latest-JN0-360-real-exam-questions    | 100%-Pass-4A0-100-Real-Exam-Questions    | Dumps-300-135-exams-date    | Passed-200-105-Tech-Exams    | Latest-Updated-200-310-Exam    | Download-300-070-Exam-PDF    | Hot-Sale-JN0-360-Exam    | 100%-Pass-JN0-360-Exams    | 100%-Pass-JN0-360-Real-Exam-Questions    | Dumps-JN0-360-exams-date    | Exam-Description-1Z0-876-dumps    | Latest-exam-1Z0-876-Dumps    | Dumps-HPE0-Y53-exams-date    | 2017-Latest-HPE0-Y53-Exam    | 100%-Pass-HPE0-Y53-Real-Exam-Questions    | Pass-4A0-100-Exam    | Latest-4A0-100-Questions    | Dumps-98-365-exams-date    | 2017-Latest-98-365-Exam    | 100%-Pass-VCS-254-Exams    | 2017-Latest-VCS-273-Exam    | Dumps-200-355-exams-date    | 2017-Latest-300-320-Exam    | Pass-300-101-Exam    | 100%-Pass-300-115-Exams    |
http://www.portvapes.co.uk/    | http://www.portvapes.co.uk/    |