> But we mostly have one memory model today - one big flat memory space, because C. This is not what is meant by 'memory model'. What is really specifies is ho

> But we mostly have one memory model today - one big flat memory space, because C. This is not what is meant by 'memory model'. What is really specifies is how memory operations can ordered and when a write made by one thread is seen by another, acquire, release, relaxed etc. For example: https://en.cppreference.com/w/cpp/atomic/memory_order https://en.cppreference.com/w/cpp/atomic/memory_order