Does Interlocked.CompareExchange use a memory barrier?

by

Any x86 instruction that has lock prefix has full memory barrier. As shown Abel’s answer, Interlocked* APIs and CompareExchanges use lock-prefixed instruction such as lock cmpxchg. So, it implies memory fence.

Yes, Interlocked.CompareExchange uses a memory barrier.

Why? Because x86 processors did so. From Intel’s Volume 3A: System Programming Guide Part 1, Section 7.1.2.2:

For the P6 family processors, locked operations serialize all outstanding load and store operations (that is, wait for them to complete). This rule is also true for the Pentium 4 and Intel Xeon processors, with one exception. Load operations that reference weakly ordered memory types (such as the WC memory type) may not be serialized.

volatile has nothing to do with this discussion. This is about atomic operations; to support atomic operations in CPU, x86 guarantees all previous loads and stores to be completed.

More Related Contents:

  1. Volatile vs. Interlocked vs. lock
  2. c# – Volatile keyword usage vs lock
  3. “A reference to a volatile field will not be treated as volatile” implications
  4. Is it possible to observe a partially-constructed object from another thread?
  5. Where is likely the performance bug here? [closed]
  6. Maximum number of threads in a .NET app?
  7. Is the C# static constructor thread safe?
  8. Implement C# Generic Timeout
  9. How to update UI from another thread running in another class
  10. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
  11. Compare using Thread.Sleep and Timer for delayed execution
  12. Re-entrant locks in C#
  13. Reducing memory usage of .NET applications?
  14. Getting the thread ID from a thread
  15. Multiple Parallel.ForEach loops in .Net
  16. What does SynchronizationContext do?
  17. How to put a task to sleep (or delay) in C# 4.0?
  18. Task continuation on UI thread
  19. Is it OK to use a string as a lock object?
  20. EF Data Context – Async/Await & Multithreading
  21. Is volatile bool for thread control considered wrong?
  22. Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
  23. Switch case on type c# [duplicate]
  24. C# : Monitor – Wait,Pulse,PulseAll
  25. Should thread-safe class have a memory barrier at the end of its constructor?
  26. Read and process files in parallel C#
  27. C# volatile variable: Memory fences VS. caching
  28. Accessing UI in a thread
  29. Calling an async method from a synchronous method
  30. Draw on a form by a separate thread

Leave a Comment