volatile and MemoryBarrier()...(blogs.msdn.com)
submitted by 
crpietschmann(11.3k) 3 years, 10 months ago
That part I knew… what we news to me is there is a better way to do volatile, and that is with an explicitly memory barrier before accessing the data member.. We have a an API for that: System.Threading.Thread.MemoryBarrier(). This is more efficient than using volatile because a volatile field requires all accesses to be barriers and this effects some performance optimizations.
|category: CLR
|Views: 27
tags:
lock MemoryBarrier CLR threading another
Everyones tags:
Your Tags: