![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#21
| ||||
| ||||
|
|
I think childishness is unique to Intel. LOL. Right...I think you have a lot to learn about the world then. All these companies have been childish. "native quad core"? |
|
Other times it's something like trying to come up with a Hypertransport work-alike, called CSI, which still somehow manages not to be compatible between all of its processor families, What does 'compatible between all CPU families' even mean in that sentence? Did you seriously expect IPF and x86 to fit into the same sockets? Or is the comment in relation to Xeon MP vs. DP? I guess I'm not sure what the complaint is. |
|
Why would Intel want to license HT? They'd need to develop their own cache coherency protocol anyways, so using different (and better) lower layers isn't a big deal. Also, it isn't clear to me that HT is suitable for the entire range of applications that Intel is targeting (that being said, I know of no evidence that it is unsuitable). |
|
Now it's all of this effort to recreate Z-RAM on bulk silicon. They are still going to have to add some SOI ontop of the bulk silicon to get this to work, now what's the point of going through all of this modification of bulk silicon to act like SOI, when SOI itself is around? And if they've announced they're going to SOI anyways, this tech will only have limited usage before they convert to SOI. They announced they'll be going to FD-SOI at some point in time. That could be 32 or 22nm for all we know... I really see no good reason for Intel to convert to PD-SOI if they are just going to be using it for a relatively short period of time. There needs to be a substantial ROI there. Also, the benefits of PD-SOI are less for smaller geometries than larger ones...so while it might represent a 1/2 generation in terms of switching speed at 130nm, it could be 1/3 or 1/4 generation at 65 or 45nm (I don't have hard numbers at my finger tips right now). |
#22
| |||
| |||
|
|
David Kanter wrote: I don't think Return On Investment is even in Intel's vocabulary. They've been swimming in monopoly money for so long that they're probably just now figuring out ROI. |
|
AMD produces at most 1/4 the silicon Intel does. IBM's even lower volume. This means that Intel generally is going to be more sensitive to increases in cost of their processes than AMD... Or exactly the opposite. Fabs are fixed cost outlays, the more you produce past your break-even point, the less you have to consider cost. |
|
Going forward Intel does have some problems, I think they are focusing too much on their current competition (AMD) and not enough on the future competitors (cell phone guys). This last comment applies just as much to AMD though... Intel has sold off all of their cell phone businesses now, so AMD is their only competitor worth worrying about. |
#23
| |||
| |||
|
|
David Kanter wrote: Right...I'm sure they did. Perhaps you mean in the Northstar design that John Borkenhagen worked on. I agree it was an early form of Multithreading, but: It is Switch on Event Multithreading (SoEMT), not Simultaneous multithreading (SMT). So, no, IBM did not do SMT before. A friend has one of the critical patents that Intel references. And...that doesn't change the fact that SMT != SoEMT. DK As Keith knows, there was a heated debate within IBM over the merits of SOI. And today the IBM Fab manufactures both bulk and SOI. The ASIC products, for example, are bulk. The microprocessors and game chips are SOI. And yes, IBM cares about yield. |
|
Northstar had one form of multithreading, the one that could be added economically. It was enough of a win that it was carried forward for several generations of processors. |
|
Neither IBM nor Intel has a monopoly on smart or stupid. Neither does AMD either. |
#24
| ||||
| ||||
|
|
Del Cecchi wrote: David Kanter wrote: Right...I'm sure they did. Perhaps you mean in the Northstar design that John Borkenhagen worked on. I agree it was an early form of Multithreading, but: It is Switch on Event Multithreading (SoEMT), not Simultaneous multithreading (SMT). So, no, IBM did not do SMT before. A friend has one of the critical patents that Intel references. And...that doesn't change the fact that SMT != SoEMT. DK As Keith knows, there was a heated debate within IBM over the merits of SOI. And today the IBM Fab manufactures both bulk and SOI. The ASIC products, for example, are bulk. The microprocessors and game chips are SOI. And yes, IBM cares about yield. There we have it...SOI is not for every product. |
|
Northstar had one form of multithreading, the one that could be added economically. It was enough of a win that it was carried forward for several generations of processors. Absolutely. I'm not denigrating SoEMT; I'm just pointing out that it's not SMT, and Keith should know better than to try to foist that fallacy on us. |
|
SoEMT is much less complex for a variety of reasons. It doesn't let you exploit unused issue slots, |
|
but it does let you get a lot of overlap for memory operations, which quite frankly, for servers (where northstar was aimed) is the key point. Neither IBM nor Intel has a monopoly on smart or stupid. Neither does AMD either. I'm inclined to agree with that; sadly it seems like other folks here are far less reasonable in their assumptions. |
#25
| |||
| |||
|
| snip |
|
Hell, you heard Del say that there was a huge internal fight over whether to use SOI or not. They aren't using SOI for everything, just the high-end stuff. |
#26
| |||
| |||
|
|
No, the real reason is cross-licenses. You're thinking that Intel has access to ZRAM through AMD's access? Or that Intel is just implementing something that they might have gotten through another source? Intel definitely doesn't have access to ZRAM through AMD, it would have to get its own license from Innovative. The Intel-AMD cross-license only affects the instruction set. |
#27
| ||||
| ||||
|
|
Yousuf Khan wrote: David Kanter wrote: I don't think Return On Investment is even in Intel's vocabulary. They've been swimming in monopoly money for so long that they're probably just now figuring out ROI. Very mature response. Intel certainly does have a concept of ROI; all corporations do. You just have to remember, the folks who make the ROI calculations at Intel actually have the best information possible. You and I don't. AMD produces at most 1/4 the silicon Intel does. IBM's even lower volume. This means that Intel generally is going to be more sensitive to increases in cost of their processes than AMD... Or exactly the opposite. Fabs are fixed cost outlays, the more you produce past your break-even point, the less you have to consider cost. Actually that's not really true. SOI wafers cost more, there are more processing steps, which slow down production, SOI wafers are incredibly fragile. etc. etc. Hell, you heard Del say that there was a huge internal fight over whether to use SOI or not. They aren't using SOI for everything, just the high-end stuff. |
|
SOI adds substantial costs, it would also force Intel to totally rework their circuit stuff, etc. etc. And frankly, SOI is worth less and less performance at every node. |
| Going forward Intel does have some problems, I think they are focusing too much on their current competition (AMD) and not enough on the future competitors (cell phone guys). This last comment applies just as much to AMD though... Intel has sold off all of their cell phone businesses now, so AMD is their only competitor worth worrying about. Intel still retains their high-end Xscales. If you think that Intel only needs to worry about AMD, and vica versa, you are sadly mistaken. How many people in China own PCs? How many people own cell phones? When I was in Tanzania, many of the adults had cell phones. PCs? Not a chance. When cell phone processors get powerful enough, AMD and Intel will have to worry; since it takes 5 years to do anything, that means they should probably have started thinking about this issue a year ago or so. DK |
#28
| |||
| |||
|
|
No matter how much you like or dislike INTC, one has to admit that INTC has enough cash on hand to buy all the licenses in the world, or at least all the licenses they need. Might cut into profit margin in case of per unit fee, but shouldn't be an unsurmountable obstacle. If I am not mistaking, INTC still gets a cut off every CPU AMD sells - or at least used to ;-) |
|
In other words, if ZRAM proves to be useful, you should expect INTC to follow AMD in using it quite soon - about as soon as they did with AMD64 - oh, pardon me, Intel doesn't do anything AMD..., they do their own superior EM64T ;-)))))))))) They sure will find more fitting, Intel-like name for ZRAM tech as well |
#29
| |||
| |||
|
|
nobody (AT) nowhere (DOT) net wrote: |
|
In other words, if ZRAM proves to be useful, you should expect INTC to follow AMD in using it quite soon - about as soon as they did with AMD64 - oh, pardon me, Intel doesn't do anything AMD..., they do their own superior EM64T ;-)))))))))) They sure will find more fitting, Intel-like name for ZRAM tech as well Well, the AMD64 instruction set was easy, it's just software. However, Z-RAM or whatever Intel calls it when it brings it out, will be quite a bit more difficult. As we can see, Intel has matched AMD's instruction set (well, it is the same instruction set after all), |
|
but it still so far hasn't countered Hypertransport and direct memory controller of AMD's K8-series. |
#30
| |||
| |||
|
|
Seriously, those folks that do the ROI calcs must cry themselves to sleep every night, at the lack of influence they have on the management over there. They save money by using old tech on one hand, but then they fritter it away by having to spend more money on R&D to get around the limitations on the other hand. I'm just amazed at the x-ray vision you seem to have into Intel. For |
|
From what I can see, Intel is a Wall-Street driven company that cares very much about what Wall Street thinks, and Wall Street understands |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |