3 ms·
> When core A writes to memory location X, then core B reads from memory location X, why do we insist that core B reads what core A wrote? Because that's what
by pjc50 6y ago
> When core A writes to memory location X, then core B reads from memory location X, why do we insist that core B reads what core A wrote?
Because that's what the Intel programmer's model of memory specifies. This is not necessarily true on ARM: https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/memory-access-ordering-part-3---memory-access-ordering-in-the-arm-architecture https://community.arm.com/developer/ip-products/processors/b...
> different cores should not be using the same region of memory
Generally known as "NUMA"; this is a viable programmer's model, but it's different from what people are used to, and requires either software changes or a lot of performance-impacting compatibility layers when software accesses pre-existing global variables.
(You could certainly get NUMA multiprocessing systems back in the day - to make effective use you had to pin processes to cores, because the cost of migrating memory about was considerable otherwise)