6 ms·
Intel details Skymont
- pclmulqdq 2y agoIt looks like the next generation of *mont cores will be as big and capable as Skylakes. With E cores like this, who needs P cores? Also, Intel was definitely onto something with the split decoders IMO. The x86 instruction set hurts to decode 8-wide in a single thread, but most code is branchy and loopy, so you only hurt in this configuration if loops are really big. Tight loops come from the uop cache, and branchy code gets 3-way decoding.
- deaddodo 2y ago> With E cores like this, who needs P cores? Because, presumably, the P-cores are even beefier. Intel and AMD are still trying to gain time on the slow march to ARM (particularly Apple) catching up. Both of their long term strategies seem to differ (AMD edging back into ARM itself, Intel being a little more close lipped), but they can't lose their one major edge (raw performance) or potentially more users switch to an x86-excluded (and, more importantly, third-party excluded) platform (Mac).
- metadat 2y agoIs ARM really that special? Why do you believe this is the case?
- thunderbird120 2y agoThe ISA is much less important than many people seem to think. The RISC vs CISC debate is beyond outdated at this point because no modern architecture actually works strictly like either under the hood. Organizations who did x86 architectures historically had much more emphasis on performance while organizations who did ARM had more emphasis on low power devices. The lingering engineering consequences of that history and the experience of the organizations doing design are orders of magnitude more relevant than the difference in actual ISA.
- Dalewyn 2y agoARM is special in that it's the only potential, realistic competitor to x86 left in the entire industry. RISC-V? Only if you're a zealot breathing fumes for life energy, at least as things stand today.
- gary_0 2y agoThe interesting thing about RISC-V is that there are like 10 billion RISC-V microcontrollers out there that otherwise would have been ARM. So ARM has been moving into the PC/server space while RISC-V pushes in from behind, at the opposite end of the line from x86.
- cptskippy 2y agoRISC-V is disrupting ARM's low end, the pace it's occupied safely for decades. As RISC-V matures, it will move upstream along the same path that ARM did. The difference is that it will be easier to move because the transition to ARM is demonstrating that companies don't need to be locked to a particular ISA.
- deaddodo 2y agoARM is simply the ISA the industry is pivoting to and where most forward investment is going. I don't know where I implied it was special.
- pclmulqdq 2y agoIn all seriousness, the main advantage of the P cores is the wider vector datapath. They are much more set up for loopy "grunt work" like matrix math. Web serving probably doesn't need a P core, for example.
- jorvi 2y ago> or potentially more users switch to an x86-excluded (and, more importantly, third-party excluded) platform (Mac). Or much more likely, Windows ARM.
- phire 2y ago> Tight loops come from the uop cache, and branchy code gets 3-way decoding. First, there is no uop cache on the "mont" cores. Second, Intel aren't decoding both sides of the branch. That wouldn't actually help much, as modern branch predictors are correct well over 99% of the time. It would be a waste of silicon and power to have an extra decoder producing work which simply decoded most of the time, and an even bigger waste to have two extra decoders. Intel's actual approach is way more clever; They run the branch predictor ahead of the decoders by at least 3 branches (probably more). The branch predictor can spit out a new prediction every cycle, and it just plops them on a queue. Each of the three decoders pops a branch prediction off the queue and starts decoding there. At any time, all three decoders will each be decoding a different basic block. A basic block that the branch predictor has predicted that the program counter is about to flow through. The three decoders are leap frogging each other. The decoding of each basic block is limited to a throughput of three instructions per cycle, but Skymont is decoding three basic blocks in parallel. The decoded uops get pushed onto three independent queues, and the re-namer/dispatcher merges these three queues back together in original program order before dispatching to the backend. Each decoder can only push three uops per cycle onto its queue, but the re-namer/dispatcher can pull them off a single queue at the rate of 9 uops per cycle. The other two queues will continue to fill up while one queue is being drained. The branch prediction result will always land on an instruction boundary, so this design allows the three decoders to combine their efforts and maintain a throughput of 9 uops per cycle, as long as the code is branchy enough. It works on loops too, as far as I'm aware, intel doesn't even have a loop stream buffer on this design; The three decoders will be decoding the exact same instructions in parallel for loop bodies. But Intel have a neat trick to make this work even on code without branches or loops. The branch predictor actually inserts fake branches into the middle of long basic blocks. The branch predictor isn't actually checking an address to see if it has a branch. Instead it predicts the gap between branches, and they simply have a limit for the size of those gaps. Looks like that limit for Skymont is 64 bytes (was previously 32 bytes for Crestmont)
- Marthinwurer 2y agoThank you for that explanation, I was confused as to what was happening with the multiple decoders. That's a wild way to implement a processor front end.
- ls612 2y agoI did the math and even on current 13900k/14900k chips each E-core is roughly equivalent to a stock Skylake 6700k core.
- skavi 2y agoThe two generation old Gracemont already beat Skylake [0]. Skymont can beat Raptor Cove [1] (The big core that was paired with Gracemont). [0]: https://www.anandtech.com/show/16881/a-deep-dive-into-intels-alder-lake-microarchitectures/4 https://www.anandtech.com/show/16881/a-deep-dive-into-intels... [1]: https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4/3 https://www.anandtech.com/show/21425/intel-lunar-lake-archit...
- wffurr 2y agoClassic disrupting yourself from below. A little late now that ARM chips from both Apple and now Qualcomm (maybe?) have caught up, but the second best time is now. I give it 2 more releases max before Intel drops heterogeneous cores and only ships the -Mont architecture.
- BearOso 2y agoAgreed. We've seen this before. Pentium M -> Core.
- dur-randir 2y ago>With E cores like this, who needs P cores? Based on their the current performance, anyone who need it.
- kristianp 2y agoSo Skymont is the architecture of the Efficiency core of Lunar lake: https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4/3 https://www.anandtech.com/show/21425/intel-lunar-lake-archit... It's so new that the Wikipedia page hasn't been written yet, it still redirects to the old usage of the codename as the previous name of Cannon Lake. Or it should redirect to a Lunar Lake page: https://en.wikipedia.org/?title=Skymont_(microarchitecture)&redirect=no https://en.wikipedia.org/?title=Skymont_(microarchitecture)&...
- _ugfj 2y ago[flagged]
- tedunangst 2y agoTIL rounding denormals to zero is what -ffast-math actually does.
- kibwen 2y agoNot sure if I should be relieved or concerned that even Ted Unangst doesn't know what -ffast-math actually does. (For the record, it does a whole lot of terrible things: https://stackoverflow.com/questions/7420665/what-does-gccs-ffast-math-actually-do https://stackoverflow.com/questions/7420665/what-does-gccs-f... )
- pclmulqdq 2y agoThere's more. It also enables some limited (unsafe) rearrangement of your floating point expressions, as well as a few other settings inside the floating point system. Flushing denorms to 0 is only part of it. It also will do things like using an approximate reciprocal square root instruction plus a refinement iteration instead of fsqrt then fdiv.
- CJefferson 2y ago-ffast-mast does a whole bunch of things, which I wish people's didn't so commonly combine. For example, I think the things it does which are sensible for most people are: * Rounding subnormals to zero * Disabling signed zeroes * Disables support for 'trapping' (throwing SIGFPE) Then there are the 'middle' things, which annoy some people: * Allow associative operations, and things like sqrt(xy)=sqrt(x)sqrt(y), exp(x)*exp(y)=exp(x+y) However, it also (which I often find break code) assumes no operation will make a NaN or an Infinity -- these last two don't really help, and also break code in confusing ways. This being gcc, they don't just change things like std::isnan or std::isinf into an 'abort' (which would make sense, in -ffast-math they don't make sense), they just return nonsense instead.
- clausecker 2y agoFor me, the most important part is -fno-math-errno which allows the compiler to ignore that libm functions are allowed to set errno. This is perfectly safe (unless you rely on that rarely known side effect) and is usually the one flag I explicitly set.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- _8j50 2y agoMore cores and memory channels+bandwidth would have been nice.
- srg0 2y agoSlightly offtopic. What would you suggest as an introductory text on modern CPU architectures?
- apples_oranges 2y agoI would start with a college/university course on the topic, there should be tons of slides and lectures available for free. And only after knowing basic concepts and common approaches I would look for some recent documents, probably they can be downloaded from Intel and other chip makers. But I would say that it all depends on where you are starting from and how deep you want to go.
- scrlk 2y agoComputer Architecture by Hennessy and Patterson is the classic introductory text. It's dated, but Inside the Machine by Jon Stokes is also a good read if you're after something a bit lighter.
- srg0 2y agoThank you!
- chainingsolid 2y agoSlightly old but relativly quick read and a good overview! https://www.lighterra.com/papers/modernmicroprocessors/ https://www.lighterra.com/papers/modernmicroprocessors/
- formvoltron 2y agoCould these processors help Intel move further into AI inference?
- null_investor 2y agoThey already have the Gaudi chip for AI, Skymont is a different kind
- wmf 2y agoIntel has the NPU for inference so it doesn't need CPU cores at all.
- giladvdn 2y agoHow do these modern Atoms compare to the Apple ARM chips? Does Apple make something comparable in terms of power/performance?
- MobiusHorizons 2y agoThe competitor would be the efficiency cores on the M-series chips. I don’t know how well they compare though. Apple doesn’t have any skus with only efficiency cores afaik. If they did it would be something like the Apple Watch, but since arm has had big.LITTLE architecture for many years there was no need to have chips with only efficiency cores to achieve efficiency.
- saagarjha 2y agoApple Watch SoCs are "just" the efficiency cores of their iPhone cousins
- adgjlsfhk1 2y agoWait, did they only fix subnormals on the E-cores or did they fix them on the P cores also? It would be really weird if they only fixed this on the E-cores, but I haven’t seen anything saying that Redwood Cove fixed this issue.