Hi, Lock mechanisms serialize the exec of a critical section which operates on shared data, normally. Do these mechanisms (spinlocks, semaphores, atomic_t) make sure that they always operate on the most actual versions of the shared data? Have I to do some *special action* to ensure this, like qualifying the shared data volatile? What mechanism exists to enforce *memory sync* anyway? /FAU -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
