4 ms·
I'm not saying it's good for the overall system. Your choice on that. I'm just saying it's a useful memory model for making sure all your memory fences are in p
by toast0 4y ago
I'm not saying it's good for the overall system. Your choice on that. I'm just saying it's a useful memory model for making sure all your memory fences are in place. If you can run your OS/application there, it's hard to find a place it won't run.
That said, Alphas were mighty fast during their prime, I don't know if that was enabled by the insane memory model or just coincidence?
- aidenn0 4y ago> That said, Alphas were mighty fast during their prime, I don't know if that was enabled by the insane memory model or just coincidence? There were many of the same people working on: - First 3 generations of DEC Alpha - StrongARM - SiByte MIPS (later purchased and rebranded by Broadcom) - PASemi POWER - PASemi was then aqui-hired by Apple for making ARM chips These don't have any particularly unifying memory model, but were all quite performant, so while this may be a different coincidence, I suspect that the people involved are more likely a contributing factor to the performance than the memory model.
- meepmorp 4y agoDon't forget forget AMD
- xxpor 4y ago>I'm just saying it's a useful memory model for making sure all your memory fences are in place. Oh for sure. It's just that it's like saying a nuclear bunker will be fine if you drop a pound of dynamite on it :) >I don't know if that was enabled by the insane memory model I have to imagine it was, especially since back then the "optimization" parts of CPUs weren't nearly as advanced as they are today (branch predictors, OOO execution that still maintains the memory model guarantees, etc). Alphas were dead before my time, but I have to imagine the tradeoff was a) their expense, and b) the time it actually took to write software and track down concurrency bugs due to everything being talked about here.