volatile and MemoryBarrier()...

submitted by crpietschmann 1 month, 22 days ago

blogs.msdn.com — 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. read more...

add a comment | category: CLR | Views: 11