3 ms·
Hey, I wanna know more, can you elaborate?
by Tinyyy 11y ago
Hey, I wanna know more, can you elaborate?
- wtallis 11y agoIntel's only got the ability to develop one microarchitecture family. When they try for more than one, things fall through the cracks and you get the Pentium 4 dead-end or the Atom's lackluster performance. Intel's primary microarchitecture is aimed at laptops. It scales reasonably down to large tablet power levels and up to workstation power levels. For the high-performance server market, they can only throw cores and cache at the problem, with some enterprise features bolted on. IBM's always targeted the high-performance server market. For a while, their Power cores were also being used for workstations and even a desktop by Apple, but that's never been the focus. They include things like decimal arithmetic and SMT and hardware transactional memory and they've been selling the high-end parts at 4-5GHz speeds for a long time.
- cbd1984 11y agoOK, what's Intel missing for high-performance servers? They've got respectable performance, they've got VT-x and all the other virtualization hardware, what's missing?
- dijit 11y agotheir underlying architecture wasn't built for it. it's like trying to build a skyscraper on the foundations of a log cabin.. you can get so far up and things will start to sink back into the mud.
- the_why_of_y 11y agoThe x86 architecture was not amenable to a high performance pipelined implementation, so what Intel did since Pentium Pro is to JIT the x86 instructions into an internal RISCy instruction set that can be executed out-of-order with competitive performance. The x86 architecture was limited to 32-bit, severely limiting the virtual address space as well as hampering OS implementation with hacks like PAE, so what AMD did is to extend it to 64-bit. The x86 architecture was not designed for SMP scalability due to the rather strict memory ordering requirements, but most of the architectures with laxer memory models (in particular, Alpha, which was the most lax of all) are out of business today (in fact, of the commercially relevant server architectures today, only POWER has lax memory ordering; SPARC can in theory but is usually configured to run with TSO which is similar to x86). The x86 architecture was not designed for OS virtualization because various instructions did not trap when executed in user mode, so what Intel and AMD did is define a new protection level ("ring -1") to run the hypervisor so this works efficiently now. What actual problem do you see with x86 that cannot be solved or worked around by some creative engineering at Intel/AMD?
- gsnedders 11y ago> The x86 architecture was not amenable to a high performance pipelined implementation, so what Intel did since Pentium Pro is to JIT the x86 instructions into an internal RISCy instruction set that can be executed out-of-order with competitive performance. POWER does the exact same (I can't remember which revision).
- gsnedders 11y agoIt's probably worthwhile to point out that Itanium still, just about, exists, and has traditionally been Intel's competitor to POWER. Though certainly, in recent years, x86_64 has largely taken over that role.