2 ms·
> requiring every CPU to implement strong memory-order guarantees is one of the things holding back frequencies How does it hold back the frequency? I would ha
by chrisseaton 7y ago
> requiring every CPU to implement strong memory-order guarantees is one of the things holding back frequencies
How does it hold back the frequency? I would have thought it would mean you can do less in each clock cycle, but not limit the frequency.
- garmaine 7y agoBecause electrical signals, required for coordination, can only travel so far in one cycle.
- chrisseaton 7y agoRight, so you need more cycles to complete each operation, don't you? Why can't you run the same number of cycles though?
- notacoward 7y agoMemory ordering isn't the kind of thing that can be neatly separated from your instruction scheduler, register file, etc. Some of the communication and checking that's necessary to maintain strong ordering has to be handled within each unit each cycle. I'm probably doing a poor job explaining it, though. Maybe someone even closer to these issues can do better.
- notacoward 7y agoThe extra complexity holds back frequencies in a couple of ways. The two that most immediately come to mind are: * More work and communication to be done per cycle means slower cycles. * More circuitry means more heat to dissipate. There are probably others, but I'm not a chip designer myself. I just sat next to a few.