<?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 Thread Data Exchange through L3 Cache in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796230#M458</link>
    <description>I guess you are asking about the situation where a thread modifies a cache line, then other threads on other cores want to read it. The updated cache line in L1 or L2 becomes the only copy which is valid, and it must be updated by copying to L3 before other cores can use it by updating their copy in L1 or L2. Cores on the same CPU don't need to wait for write back to memory, as cores on the other CPU must do.</description>
    <pubDate>Wed, 23 Feb 2011 18:31:24 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2011-02-23T18:31:24Z</dc:date>
    <item>
      <title>Thread Data Exchange through L3 Cache</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796229#M457</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have hopefully a quick question...&lt;/P&gt;&lt;P&gt;I'm using a dual socket quad core (HT) Xeon X5570. It is a NUMA machine with each core having its own L1 and L2 caches and each socket's cores share a single L3 cache on the die. My question revolves around access and coherence specifically with the shared L3 cache.&lt;/P&gt;&lt;P&gt;I'm looking to have the most efficient communication between threads that will only run on cores on the same socket sharing the same L3 cache. I'm looking to do this through having a shared memory block (an array) that is only accessed by threads on the same socket/L3 cache. If only these threads access this array (so no other cores on different sockets will access it), will write backs to main memory be required? I'm intersted in what the specific cache coherency mechanics will be under this scenario?&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brandon&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2011 23:06:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796229#M457</guid>
      <dc:creator>bmeardon</dc:creator>
      <dc:date>2011-02-22T23:06:18Z</dc:date>
    </item>
    <item>
      <title>Thread Data Exchange through L3 Cache</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796230#M458</link>
      <description>I guess you are asking about the situation where a thread modifies a cache line, then other threads on other cores want to read it. The updated cache line in L1 or L2 becomes the only copy which is valid, and it must be updated by copying to L3 before other cores can use it by updating their copy in L1 or L2. Cores on the same CPU don't need to wait for write back to memory, as cores on the other CPU must do.</description>
      <pubDate>Wed, 23 Feb 2011 18:31:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796230#M458</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-02-23T18:31:24Z</dc:date>
    </item>
    <item>
      <title>Thread Data Exchange through L3 Cache</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796231#M459</link>
      <description>I thought that would be the answer and that confirms it. Thank you TimP!</description>
      <pubDate>Wed, 23 Feb 2011 18:54:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Thread-Data-Exchange-through-L3-Cache/m-p/796231#M459</guid>
      <dc:creator>bmeardon</dc:creator>
      <dc:date>2011-02-23T18:54:52Z</dc:date>
    </item>
  </channel>
</rss>

