Intel Broadwell Architecture Preview: A Glimpse into Core M
anandtech.com
anandtech.com
very cool.
Not that it will necessarily be the absolute end of Moore's law, as hardware manufacturers are trying alternative approaches to keep ramping up power, e.g. Samsung already sells its 850 Pro series SSDs http://www.amazon.com/s/ref=nb_sb_ss_c_0_6?url=search-alias%... made with its VNAND memory http://www.samsung.com/global/business/semiconductor/html/pr... which fell back to 40 nm from 840 EVO's 19 nm, while going 3D, which seemed to improve both speed and reliability. Now they have a bit more runway in their Moore's law, but still not much in sight.
I know this probably wouldn't work for a mobile device but for desktops/servers theres a ton of room for larger dimension chips right?
So yes you can. But if you do this for more then 26 months we'll end up with 600 watt CPU's.
To be technical, Moore's law is about the number of transistors on an integrated circuit.
So your point isn't too far off the 3D comments elsewhere.
Simply making the die bigger doesn't get you much: larger dies (without additional redundancy) have lower yields (as you're more likely to have a defect given a constant defect/area rate) and fewer can be stamped out of a standard sized wafer.
However, if you carry that idea to its logical conclusion... we may turn from shrinking the transistor to shrinking the packaging as the path of least resistance. 3D transistors, chip stacking (aka PoP), and through-silicon vias (aka vertical connectivity) all help get us more processing / area (while remaining within fundamental thermal, manufacturing, etc. physical limits).
Again, this is a CS major with an architecture interest, so anyone please feel free to correct me if I'm off-base.
If you go 3D, you need a very large drop in heat dissipation to keep your junction temperatures down.
Silicon photonics is likely to be a huge source of potential improvements. A former Intel SVP, Pat Gelsinger, was quoted as saying "Today, optics is a niche technology. Tomorrow, it's the mainstream of every chip that we build." http://en.wikipedia.org/wiki/Silicon_photonics
But you'll be in quite a bad situation if it does not propagate through at least an entire ALU and register file within less than a cycle. Not an impossible situation, but a bad one.
Imagine a scratch that runs straight through the middle of several chips parallel to 2 out of the 4 sides and runs for 175 millimeters. If the chips are 50mm x 50mm each, you would lose at most 12,500 sq mm of silicon (3 scratched through and 2 with 12.5mm scratches = 5 * 2500 sq mm). If they are, say, 60mm x 60mm you could lose 14,400 sq mm of silicon from the same error (2 scratched through and 2 with 12.5 mm scratches = 4 x 3600 sq mm).
Intel, on the other hand, needs to be able to sell as many chips as possible per wafer, because they have vastly lower margins. This is also why they do stuff like fusing off dead cores and cache to produce working lower-end parts from dice that aren't 100% functional out of the factory.
[0] https://en.wikipedia.org/wiki/IBM_z196_%28microprocessor%29
[1] Locked-in customer base, service costs dwarf hardware costs, etc.
For CPUs, it's not done at any granularity finer than a whole core - nobody sells CPUs that might have one of the ALUs disabled.
http://thememoryguy.com/comparing-samsung-v-nand-to-micron-1...
The only thing i'm sure of, when Moore's law ends we'll be spending a lot more time with Amdahl's law.
Execution time after improved=
(execution time affected by improvement / amount of improved)+Execution time unaffected.
EDIT: i7 details
The things a bit overpowered even for its use as is. I even started setting up vm's on the box to give it more to do.
I also love these low power cpus for desktops/home systems. When they use less power than a lightbulb, i'm all for it.
So don't lump all the mobile parts in with the ultrabook-optimised chips.
If Broadwell can bring 20W quadcore i5/i7 - that would be even better! Currently only BayTrail Pentium J can offer that.
The part is 25w TDP, but there are passive heatsinks for it, but even with the fan I have it at 25% speed and its quieter than a mechanical hard drive.
The performance is something else entirely from the super low power NUC stuff. Video editing and processing is suddenly not a problem.
I got the H1 from HD-Plex.com myself. It's specified to cool 55W but I run the 65W version of the i7 (so it's semi-low power) without any problems, not even at full load for extended periods of time.
It takes mini-ITX motherboards and stuffing it with 16 GB RAM was not a problem. It was a bit fiddly to everything together but the build quality is great.
No relation, just a satisfied customer.
I've been trying to work out what spec I can power off a PicoPSU and this becomes important when the TDP is all I have to go on for power consumption figures.
The Macbook Pro Retinas already use the onboard Intel GPUs on all but the highest-end models, and they'll only be more powerful with Broadwell I suspect.
Hell, Adreno from Qualcomm can probably drive 4k.
Desktops, compositing, and light effects like transparency are nothing next to video game or 3d model rendering. In practice, any GPU manufactured today is enough for non-3d purposes, unless you try running 3 4k monitors off the numberless hd graphics or something.
If you aren't getting 60 fps scrolling, it is usually due to the cpus being low powered and the application not using GL accelerated drawing for the scrolling.
MULX was introduced on Haswell as part of the BMI instructions. Basically it allows two explicit destinations (still an implied rdx source though).
ADCX/ADOX are pretty weird. They both operate basically the same as ADC, but only read/write the carry or overflow flag respectively. The idea is to allow two interleaved independent chains of adds, putting less pressure on the out-of-order logic on chip. This seems kinda weird though: the renaming logic would have to detect that the bit of the flags register that one chain of adds reads aren't written by the other chain, so those instructions wouldn't be hazards, and thus both chains can be executed in parallel. OTOH, IIRC there are other instructions that only write certain bits of the flags, so I guess the logic for this bit-level renaming of flags is already there.