http://msmvps.com/blogs/luisabreu/archive/2009/07/03/multithreading-using-fences-from-net-code.aspxIn the last post , we’ve talked about memory fences. Today we’re going to keep looking at this topic, but we’re turning our attention to coding, ie, we’re going to talk about the options we have to add fences to our classes. In .NET, things are relativelyenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/luisabreu/archive/2009/07/03/multithreading-using-fences-from-net-code.aspx#1698395Mon, 06 Jul 2009 11:27:26 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1698395Ivan Kotev<p>One small addition. In their current implementation VolatileRead and VolatileWrite use full memory fence. The internal implementation(Of course that can be changed) is:</p> <p>public static int VolatileRead(ref int address)</p> <p>{</p> <p> &nbsp; &nbsp;int num = address;</p> <p> &nbsp; &nbsp;MemoryBarrier();</p> <p> &nbsp; &nbsp;return num;</p> <p>}</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1698395" width="1" height="1">