4 ms·
Remember, within a generation these chips are almost all made from the same set of masks. None of these disabled features save any transistors or die area; the
by wtallis 12y ago
Remember, within a generation these chips are almost all made from the same set of masks. None of these disabled features save any transistors or die area; the disabling just leaves you with a dead spot on the chip. So the real question is if you've got the hardware in place to provide these special features, can you save any power by not using those features?
The answer is that you only save power by not doing at all the things those features accelerate. It's never more efficient to implement AES through general-purpose instructions than using the fixed-function hardware. If you've got a workload that can benefit from the wider SIMD units, it won't save any energy to only use the narrower instructions. If you're trying to secure or virtualize your OS, doing it with VT-x and VT-d will be so much faster than emulating it in software that even if those features added several watts to the chips power consumption you would still save energy.
Doing less can save power, but doing the same amount of stuff the hard way doesn't help anything.
- tanderson92 12y agoThat's only true if you are using those features 100% of the time though, right ? By which I mean, there is no doubt a trade-off in play when you only use the features for 15% of your workload. This is because the chip must be powered on all the time but, say, the software implementation of AES doesn't always have to be running.
- wtallis 12y agoNo, special-purpose functional units are very well power-gated on modern chips. They don't draw appreciably more power when not in use than when fused off.
- rasz_pl 12y agoyou say that, but in practice Intel is still 5-10x off ARM when it comes to idle power.
- wmf 12y agoIs that true for Merrifield/Moorefield? AFAIK they're pretty close, but only in the phone chips.
- wtallis 12y agoRegister renaming and instruction reordering and things like that can't be selectively powered down, and are very power-hungry. But if you were talking about when the entire core is suspended, then that's largely unrelated to the high-level feature set of the processor. It's about things like the analog characteristics of the transistors used: Intel builds their mainstream CPUs using circuits that can run at 4-5GHz without trouble while none of the mobile SoCs can come close regardless of exotic cooling.
- dippyskoodlez 12y agoYou can also disable defective components without being forced to bin the entire chip to a recycle bin. That is honestly probably more of a factor than anything for the segregation between models. Get that yield up to improve margins significantly.
- wtallis 12y agoDisabling whole cores or lumps of cache to improve yields is one thing, but a lot of the features Intel is segmenting the market with are very tightly integrated with the rest of the chip. It would be extremely hard to detect and classify a defect as affecting HyperThreading or VT-x but leaving the core otherwise functional. It's a bit more plausible that defects in the high half of a vector SIMD unit could leave you with a SSE-capable but AVX-defective chip, but I suspect that in practice any broken functional units are treated as rendering the entire core inoperable.
- nkurz 12y agoRemember, within a generation these chips are almost all made from the same set of masks. None of these disabled features save any transistors or die area I think it might be true for CPUID/stepping, but not for what are usually considered to be the generations. For example, there look to be at least 5 dies sizes for Sandy Bridge: http://en.wikipedia.org/wiki/Sandy_Bridge#Models_and_steppings http://en.wikipedia.org/wiki/Sandy_Bridge#Models_and_steppin... I haven't tried to match up the supported ISA's with the different die sizes, but I presume they'd correlate. Do they not?
- wtallis 12y agoThe quad-core Sandy Bridge could end up labeled as a Core i5, Core i7, or Xeon E3. The dual core Sandy Bridge could be labeled as a Pentium, Celeron, Core i3, Core i5, Core i7 (mobile), or Xeon E3. The server designs (LGA2011) have QPI links and may be the only memory controllers capable of using registered memory. But among the processors targeting the LGA1155 and mobile platforms, they only had one core design and only one memory controller design that was shared across all products though never with everything enabled at once.
- nkurz 12y agoYes, I agree, number of cores and size of L3 are commonly cases cases where functionality is disabled. But do you know which of the other factors listed in the article that this is true for? For example, are there cases where two processors share the same die but one supports AVX and the other does not? I don't know the answer, but if there are not, this would substantially undercut the argument in the main article.
- wtallis 12y agoSandy Bridge and Ivy Bridge Celerons and Pentiums use the same die as the corresponding Core i3s, but only the i3 supports AVX in the CPU and QuickSync in the GPU. AES instructions aren't available on the i3 but are present on the dual-core i5. Haswell no longer discriminates with QuickSync, and extends AES down to the i3s but still not the Celerons and Pentiums. None of these features are unavailable due to being physically absent. They're just turned off. If Intel's microcode format and DRM were reverse engineered, some of the features could be turned back on.