Linked Questions

What is the difference between Interlocked.Exchange and Volatile.Write? Both methods update value of some variable. Can someone summarize when to use each of them? Interlocked.Exchange Volatile.Write ...

I've seen some lock free implementations of stack... My question is regarding the visibility, not atomicity. For example do elements(not pointers) of lock free stack must be at most 64bit? I think so, ...

Consider an atomic read-modify-write operation such as x.exchange(..., std::memory_order_acq_rel). For purposes of ordering with respect to loads and stores to other objects, is this treated as: a ...

EDIT/Notice: Event is now thread-safe in current F# implementation. I'm working a lot with asynchronous workflows and agents in F#. While I was going a little bit deeper into events I noticed that ...

I got a book about programming in C#. There is an example. Let me copy and paste the context. ...Introduced the usage of Interlocked(omitted here). You can also use the CompareExchange method. ...

As per this question's answer, it seems that LOCK CMPXCHG on x86 actually causes a full barrier. Presumably, this is what Unsafe.compareAndSwapInt() generates under the hood as well. I am struggling ...

It looks like the mono implementation has no MemoryBarrier calls inside the ReaderWriterLockSlim methods. So when I make any changes inside a write lock, I can receive old cached values in another ...

Trying to understand .net's memory model when it comes to threading. This question is strictly theoretical and I know it can be resolved in other ways such as using a lock or marking _task as volatile....

I have a program which is occasionally malfunctioning and I'm wondering whether the problems might be related to different threads running on different cores handling reads and writes in a different ...

Does memory barrier ensure data coherence across threads when there is no locking and no concurrent data access except from the parent thread ? Here is my scenario : the Main thread launch several ...

Suppose you have a property public Foo Bar { get; } that you want to lazily initialize. One such approach might be to use the Interlocked class, which guarantees atomicity for certain sequences of ...

Given a scenario where there's a function that should only be executed by one thread at any given time, and the rest just return (since a specific state is already being worked on), what's the best ...

I see following code in C# usage of InterLocked: class MyObj { // some class code .. int myVal public void foo() { int currVal = 0, newVal = 0; do { ...