The need for volatile modifier in double checked locking in .NET

by

Volatile is unnecessary. Well, sort of**

volatile is used to create a memory barrier* between reads and writes on the variable.
lock, when used, causes memory barriers to be created around the block inside the lock, in addition to limiting access to the block to one thread.
Memory barriers make it so each thread reads the most current value of the variable (not a local value cached in some register) and that the compiler doesn’t reorder statements. Using volatile is unnecessary** because you’ve already got a lock.

Joseph Albahari explains this stuff way better than I ever could.

And be sure to check out Jon Skeet’s guide to implementing the singleton in C#

update:
*volatile causes reads of the variable to be VolatileReads and writes to be VolatileWrites, which on x86 and x64 on CLR, are implemented with a MemoryBarrier. They may be finer grained on other systems.

**my answer is only correct if you are using the CLR on x86 and x64 processors. It might be true in other memory models, like on Mono (and other implementations), Itanium64 and future hardware. This is what Jon is referring to in his article in the “gotchas” for double checked locking.

Doing one of {marking the variable as volatile, reading it with Thread.VolatileRead, or inserting a call to Thread.MemoryBarrier} might be necessary for the code to work properly in a weak memory model situation.

From what I understand, on the CLR (even on IA64), writes are never reordered (writes always have release semantics). However, on IA64, reads may be reordered to come before writes, unless they are marked volatile. Unfortuantely, I do not have access to IA64 hardware to play with, so anything I say about it would be speculation.

i’ve also found these articles helpful:
http://www.codeproject.com/KB/tips/MemoryBarrier.aspx
vance morrison’s article (everything links to this, it talks about double checked locking)
chris brumme’s article (everything links to this)
Joe Duffy: Broken Variants of Double Checked Locking

luis abreu’s series on multithreading give a nice overview of the concepts too
http://msmvps.com/blogs/luisabreu/archive/2009/06/29/multithreading-load-and-store-reordering.aspx
http://msmvps.com/blogs/luisabreu/archive/2009/07/03/multithreading-introducing-memory-fences.aspx

More Related Contents:

  1. Singleton double-check concurrency issue
  2. Volatile vs. Interlocked vs. lock
  3. What is a singleton in C#?
  4. Is the C# static constructor thread safe?
  5. Unity singleton manager classes
  6. Thread Safe C# Singleton Pattern
  7. Singleton by Jon Skeet clarification
  8. Does Interlocked.CompareExchange use a memory barrier?
  9. Singleton Pattern for C# [closed]
  10. Serialize a Static Class?
  11. c# – Volatile keyword usage vs lock
  12. Dependency Injection vs Service Location
  13. How to avoid multiple instances of windows form in c#
  14. What is the “volatile” keyword used for?
  15. WPF: Cannot reuse window after it has been closed
  16. How to implement a singleton in C#?
  17. getting db connection through singleton class
  18. Illustrating usage of the volatile keyword in C#
  19. Should Interlocked.CompareExchange also a volatile variable?
  20. Difference between Interlocked.Exchange and Volatile.Write?
  21. Why choose a static class over a singleton implementation?
  22. C# volatile variable: Memory fences VS. caching
  23. Singleton with parameters
  24. “A reference to a volatile field will not be treated as volatile” implications
  25. C# DateTime to “YYYYMMDDHHMMSS” format
  26. Must declare scalar variable @Id?
  27. Private inner classes in C# – why aren’t they used more often?
  28. Change File Extension Using C#
  29. Change color of text within a WinForms RichTextBox [duplicate]
  30. How to Programmatically Scroll a Panel

Leave a Comment