Reading an int that’s updated by Interlocked on other threads

by

I’m a firm believer in that if you’re using interlocked to increment shared data, then you should use interlocked everywhere you access that shared data. Likewise, if you use insert you favorite synchronization primitive here to increment shared data, then you should use insert you favorite synchronization primitive here everywhere you access that shared data.

int localNumberOfUpdates = Interlocked.CompareExchange(ref numberOfUpdates, 0, 0);

Will give you exactly what your looking for. As others have said interlocked operations are atomic. So Interlocked.CompareExchange will always return the most recent value. I use this all the time for accessing simple shared data like counters.

I’m not as familiar with Thread.VolatileRead, but I suspect it will also return the most recent value. I’d stick with interlocked methods, if only for the sake of being consistent.

Additional info:

I’d recommend taking a look at Jon Skeet’s answer for why you may want to shy away from Thread.VolatileRead(): Thread.VolatileRead Implementation

Eric Lippert discusses volatility and the guarantees made by the C# memory model in his blog at http://blogs.msdn.com/b/ericlippert/archive/2011/06/16/atomicity-volatility-and-immutability-are-different-part-three.aspx. Straight from the horses mouth: “I don’t attempt to write any low-lock code except for the most trivial usages of Interlocked operations. I leave the usage of “volatile” to real experts.”

And I agree with Hans’s point that the value will always be stale at least by a few ns, but if you have a use case where that is unacceptable, its probably not well suited for a garbage collected language like C# or a non-real-time OS. Joe Duffy has a good article on the timeliness of interlocked methods here: http://joeduffyblog.com/2008/06/13/volatile-reads-and-writes-and-timeliness/

More Related Contents:

  1. Lock-free multi-threading is for real threading experts
  2. Create Dynamic Threads in c# [closed]
  3. What’s wrong with using Thread.Abort()
  4. Volatile vs. Interlocked vs. lock
  5. How do I abort/cancel TPL Tasks?
  6. Cross-thread operation not valid [duplicate]
  7. BackgroundWorker RunWorkerCompleted Event
  8. How do I run a simple bit of code in a new thread?
  9. How to wait for a BackgroundWorker to cancel?
  10. C# Thread Termination and Thread.Abort()
  11. Cancelling a pending task synchronously on the UI thread
  12. Updating an ObservableCollection in a separate thread
  13. ConfigureAwait pushes the continuation to a pool thread
  14. Unable to use more than one processor group for my threads in a C# app
  15. lowering priority of Task.Factory.StartNew thread
  16. How to catch exceptions from a ThreadPool.QueueUserWorkItem?
  17. Creating threads – Task.Factory.StartNew vs new Thread()
  18. C#/.NET analysis tool to find race conditions/deadlocks
  19. Show Loading animation during loading data in other thread
  20. C# Windows Forms Application – Updating GUI from another thread AND class?
  21. How to interrupt Console.ReadLine
  22. Error: Must create DependencySource on same Thread as the DependencyObject even by using Dispatcher
  23. How to get awaitable Thread.Sleep?
  24. Thread Safe Properties in C#
  25. Wait for pooled threads to complete
  26. Catching Error when using Task.Factory
  27. The lack of non-capturing Task.Yield forces me to use Task.Run, why follow that?
  28. Starting a new thread in a foreach loop
  29. Async and Await with For Loop [duplicate]
  30. Calling an async method from a synchronous method

Leave a Comment