3 ms·
> I would assume that a more strict memory model would be enabled only for processes that needs it (ie, Rosetta translated ones). So a cpu-flag is set/cleared w
by monocasa 6y ago
> I would assume that a more strict memory model would be enabled only for processes that needs it (ie, Rosetta translated ones). So a cpu-flag is set/cleared when entering/exiting user mode for those processes. Does this require a separate/special cache coherency protocol?
The benefits you'd get from going to a weaker memory model are by not having that extra coherency in the critical path in the first place. Adding extra muxes in front of it to make it optional would be worse than just having it on all the time.
> A complete L1d flush when entering/leaving these processes (across all CPUs)?
That wouldn't help because two threads could be running at the same time on different cores against their respective L1 and store buffers.
- andoma 6y ago> The benefits you'd get from going to a weaker memory model are by not having that extra coherency in the critical path in the first place. Adding extra muxes in front of it to make it optional would be worse than just having it on all the time. Indeed true, good point. > That wouldn't help because two threads could be running at the same time on different cores against their respective L1 and store buffers. Of course, this was related to the cost of switching coherency protocol during context switch. But as you say the overhead of just making it switchable is prohibitive in itself.