3 ms·
It sounds like Skylake is better at isolating sub-threads via result dependencies AND/OR it has more resources to utilize for your particular example. I wonder
by mjevans 10y ago
It sounds like Skylake is better at isolating sub-threads via result dependencies AND/OR it has more resources to utilize for your particular example.
I wonder if it has some form of adaptation based on how likely it feels the parallelism is to pay off versus the power cost of that failure.
- nkurz 10y agoI believe the difference is that Skylake removed a bottleneck on the number of µops that can be sustained at some stage other than the execution units, but I'm not sure where. In the example I gave, the ADD from memory is an example of micro-fusion. It's held as a single "complex" µop in the DSB, but is "un-laminated" in to 2 for execution and retirement. The CMP/JCC pairs use macro-fusion, and are combined to form a single µop both in the queue and during execution. It's documented that Skylake increased the number of µops that can be transferred from the DSB (Decoded Instruction Cache) to the IDQ (Instruction Decode Queue) from 4 µops per cycle to 6 µops per cycle. But by these metrics, we're only pulling 4 µops (representing 6 instructions) per cycle from the DSB, but these expand to 6 µops (not the same as the 6 instructions) at execution and retirement. I'm guessing that they improved the retirement bandwidth as well, but I haven't been able to find a clear statement of this, or what the new limits are.