News for hackers. Stuff that matters.
Re:How IBM Stacks Up Power8 Against Xeon Servers by dijit on Wednesday October 14, 2015 @04:44AM (#10385578)
their 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.

Re:How IBM Stacks Up Power8 Against Xeon Servers by the_why_of_y on Wednesday October 14, 2015 @05:44AM (#10385754)
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.

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?

Re:How IBM Stacks Up Power8 Against Xeon Servers by gsnedders on Wednesday October 14, 2015 @07:23AM (#10385991)
> 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).