<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RCU+SMR, hazard pointers without memory barriers in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987428#M5883</link>
    <description>You can find a working prototype at&lt;BR /&gt;&lt;A href="http://sourceforge.net/projects/atomic-ptr-plus/" target="_blank"&gt;http://sourceforge.net/projects/atomic-ptr-plus/&lt;/A&gt;&lt;BR /&gt;in the fastsmr package.  It works on Linux for ia32 and for OS X for 32 bit powerpc.  On a 866 mhz P3 a hazard pointer load with memory barriers is about 78 nsec and without memory barriers is about 11 nsec.  On a 1.2 ghz ppc it's 115 and 10 nsec respectively.  Not too bad when you let the pipelining do its stuff.  This is probably the fastest lock-free read access method around that will scale well in a multiprocessor environment.</description>
    <pubDate>Wed, 03 Aug 2005 09:11:03 GMT</pubDate>
    <dc:creator>jseigh</dc:creator>
    <dc:date>2005-08-03T09:11:03Z</dc:date>
    <item>
      <title>RCU+SMR, hazard pointers without memory barriers</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987426#M5881</link>
      <description>quick test before I spend another half hour typing in something that will disappear.</description>
      <pubDate>Wed, 29 Jun 2005 06:29:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987426#M5881</guid>
      <dc:creator>jseigh</dc:creator>
      <dc:date>2005-06-29T06:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: RCU+SMR, hazard pointers without memory barriers</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987427#M5882</link>
      <description>There was some discussion here&lt;BR /&gt;&lt;A href="http://www.ussg.iu.edu/hypermail/linux/kernel/0505.1/0252.html" target="_blank"&gt;http://www.ussg.iu.edu/hypermail/linux/kernel/0505.1/0252.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I won't retype in my original post so as to not tempt the&lt;BR /&gt;activex daemons that lurk in Intel's html. :)</description>
      <pubDate>Wed, 29 Jun 2005 06:37:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987427#M5882</guid>
      <dc:creator>jseigh</dc:creator>
      <dc:date>2005-06-29T06:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: RCU+SMR, hazard pointers without memory barriers</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987428#M5883</link>
      <description>You can find a working prototype at&lt;BR /&gt;&lt;A href="http://sourceforge.net/projects/atomic-ptr-plus/" target="_blank"&gt;http://sourceforge.net/projects/atomic-ptr-plus/&lt;/A&gt;&lt;BR /&gt;in the fastsmr package.  It works on Linux for ia32 and for OS X for 32 bit powerpc.  On a 866 mhz P3 a hazard pointer load with memory barriers is about 78 nsec and without memory barriers is about 11 nsec.  On a 1.2 ghz ppc it's 115 and 10 nsec respectively.  Not too bad when you let the pipelining do its stuff.  This is probably the fastest lock-free read access method around that will scale well in a multiprocessor environment.</description>
      <pubDate>Wed, 03 Aug 2005 09:11:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/RCU-SMR-hazard-pointers-without-memory-barriers/m-p/987428#M5883</guid>
      <dc:creator>jseigh</dc:creator>
      <dc:date>2005-08-03T09:11:03Z</dc:date>
    </item>
  </channel>
</rss>

