Volatile vs VolatileRead/Write?

Question

I can\'t find any example of VolatileRead/write (try...) but still:

When should I use volatile vs VolatileRead?

Answer 1

To Elaborate more on aleroot's answer.

Volatile.Read and Volatile.Write are same as volatile modifier as Royi Namir's argument. But you can use them wisely.

For example if you declare a field with volatile modifier then every access to this field whether it is read or write operation it will be read from CPU Register which is not free, this is not required in most of cases and will be unnecessary performance hit if field is even have many read operation.

Think of scenario where you have private singleton variable is declared as volatile and is returned in property getter, once it is initialized you don't need to read it's root from CPU Register hence you can use Volatile.Read / Write until it's instance created, once created all read operation can be done as normal field otherwise it would be big performance hit.

Whereas you can use Volatile.Read or Volatile.Write on demand bases. Best uses is declare field without volatile modifier and use Volatile.Read or Volatile.Write when needed.