2 ms·
The idea of memory being a shared scratch space for multiple cpus makes a lot of sense for a first order design perspective, but it really no longer holds. CPUs
by sitkack 6y ago
The idea of memory being a shared scratch space for multiple cpus makes a lot of sense for a first order design perspective, but it really no longer holds. CPUs are now distributed systems and should acknowledge that.
What do you think about each CPU owning its own memory region and that to send values to other CPUs, one would have to do a send, either symbolically or physically, that could be implementation dependent.
Abstractions that aren't total and sound are insufficient and should be flagged by the compiler.
- a1369209993 6y ago> to send values to other CPUs, one would have to do a send, either symbolically or physically The funny thing is, that pretty much is what store-release is (with load-acquire being the corresponding recv), anyway, just without any memory safety or sanity-checking.
- a1369209993 6y ago> without any memory safety Actually, I think that would be memory protection, not safety.
- Animats 6y agoYes. We're there already, with "sharability regions". So far, only the OS has to deal with that; each process (always?) is in one sharability region. (Shared memory between processes, though - how does that work now on machines with sharability regions?) Total sharability slows down systems with large numbers of CPU cores. We're seeing the hardware features appear to allow for less sharability. It's not being used much yet. These have programming implications, and OSs and languages have to keep up. Probably more the OS for now, with groups of CPUs and areas of memory dedicated to each other. Can Linux cgroups be used that way? This has to be invisible to the application programmer, somehow. Or we'll have another hard to program mess like the Cell.