6 ms·
2015. A good exercise would be "What's new in CPUs since 2015?" A few I can think of: branch target alignment has returned as a key to achieving peak optimizati
by jeffbee 5y ago
2015. A good exercise would be "What's new in CPUs since 2015?" A few I can think of: branch target alignment has returned as a key to achieving peak optimization, after a brief period of irrelevance on x86; x86 user-space monitor/wait/pause have exposed for the first time explicit power controls to user programs.
One thing I would have added to "since the 80s" is the x86 timestamp counter. It really changed the way we get timing information.
- titzer 5y agoSpectre. It was a vulnerability before 2015, but not known publicly until early 2018. It's hugely disruptive to microarchitecture, particularly with crossing kernel/user space boundaries, separating state between hyperthreads, etc.
- code_biologist 5y ago100%. Feasible timing attacks mean we must look at all speculative execution with suspicion. But dang that's a lot of performance to give up.
- jcranmer 5y agoIntel PT is another thing that's worth calling out since 2015 (see the other article on the front page right now, https://news.ycombinator.com/item?id=31121319 https://news.ycombinator.com/item?id=31121319, for something that benefits from it). It does look like Hardware Lock Elision/Transactional Memory is something that seems like it will be consigned to the dustbins of history (again).
- jeffbee 5y agoIntel did not ship even one working implementation of TSX, so it's not like anyone will be inconvenienced that they cancelled it.
- bcrl 5y agoA number of companies invested in doing the software development to take advantage of TSX (as the performance improvements helped databases by companies like Oracle), so Intel certainly lost a lot of credibility. And Intel is jerking software developers around again with the latest vector instructions that keep getting turned off in desktop / laptop SKUs and only being available on servers. Intel has done quite poorly over the past 5+ years on this front.
- flakiness 5y agoBig.Little-like architecture? Even intel has adopted that in their 12 gen. I believe a lot has happened around mobile and power as well. Apple boasts their progress every year, and at least some of them are real. But they are too secretive to talk about that. I hope some competitors have written some related papers. For example, the OP talks about dark silicon. What's going on around it these days?
- terafo 5y agoAFAIK Big.Little-like architectures weren't a thing in PC space only because of the scheduling problems, which is mostly a software limitation. > I hope some competitors have written some related papers. You should read this:) http://people.engr.tamu.edu/djimenez/pdfs/exynos_isca2020.pdf http://people.engr.tamu.edu/djimenez/pdfs/exynos_isca2020.pd...
- dragontamer 5y agoL3 caches have grown monstrously. The new AMD Ryzen 5800x3d has 96MB of L3 cache. This is so monstrous that the 2048x entry TLB with 4kB pages only can access 8MB. That's right, you run out of TLB-entries before you run out of L3 cache these days. (Or you start using hugepages damn it) ---------- I think Intel's PEXT and PDEP was introduced around 2015-era. But AMD chips now execute PEXT / PDEP quickly, so its now feasible to use it on most people's modern systems (assuming Zen3 or a 2015+ era Intel CPU). Obviously those instructions don't exist in ARM / POWER9 world, but they're really fun to experiment with. PEXT / PDEP are effectively bitwise-gather and bitwise-scatter instructions, and can be used to perform extremely fast and arbitrary bit-permutations. I played around with them to implement some relational-database operations (join, select, etc. etc.) over bit-relations for the 4-coloring theorem. (Just a toy to amuse myself with. A 16-bit bitset of "0001_1111_0000_0000" means "(Var1 == Color4 and Var2==Color1) or (Var2==Color2)". There's probably some kind of tight relational algebra / automatic logic proving / binary decision diagram / stuffs that you can do with PEXT/PDEP. It really seems like an unexplored field. ---- EDIT: Oh, another big one. ARMv8 and POWER9 standardized upon the C++11 memory model of acquire-release. This was inevitable because Java and C++ standardized upon the memory model in the 00s / early 10s, so chips inevitably would be tailored for that model.
- seoaeu 5y ago> That's right, you run out of TLB-entries before you run out of L3 cache these days. This is more reasonable than it sounds. A TLB miss can in many cases be faster than a L3 cache hit
- jeffbee 5y agoIt's also misleading because it has 8 cores and each of them has 2048 l2 TLB entries. Altogether they can cover 64MiB of memory with small pages.
- dragontamer 5y agoBut 5800x3D has 96MB of L3. So even if all 8 cores are independently working on different memory addresses, you still can't cover all 96MB of L3 with the TLB. EDIT: Well, unless you use 2MB hugepages of course.