I agree, the lesson from the post isn't multi-threaded==bad. Processes just make you think more about the data interactions. However, if you are in a multi-pr

I agree, the lesson from the post isn't multi-threaded==bad. Processes just make you think more about the data interactions. However, if you are in a multi-process model and using shared memory, you'd better be getting a semaphore for both memcpy and reading. So, get semaphore, do memcpy, release semaphore (all readers should be blocked during that time). Not really efficient, neither is constantly doing a memcpy on static data.