<?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 KMP_MALLOC vs allocate in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959387#M5292</link>
    <description>&lt;DIV&gt;When running within an OpenMP thread does the Fortran allocate obtain memory from the thread local heap as does KMP_MALLOC?&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;Jim Dempsey&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Sat, 03 Dec 2005 04:18:03 GMT</pubDate>
    <dc:creator>jim_dempsey</dc:creator>
    <dc:date>2005-12-03T04:18:03Z</dc:date>
    <item>
      <title>KMP_MALLOC vs allocate</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959387#M5292</link>
      <description>&lt;DIV&gt;When running within an OpenMP thread does the Fortran allocate obtain memory from the thread local heap as does KMP_MALLOC?&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;Jim Dempsey&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 03 Dec 2005 04:18:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959387#M5292</guid>
      <dc:creator>jim_dempsey</dc:creator>
      <dc:date>2005-12-03T04:18:03Z</dc:date>
    </item>
    <item>
      <title>Re: KMP_MALLOC vs allocate</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959388#M5293</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Hi Jim,&lt;/P&gt;
&lt;P&gt;The Fortran ALLOCATE intrinsic function does not allocate memory from the thread stack, even if it is called within an OpenMP parallel region. Thread stacks are generally small and it's not always necessary to allocate memory in thread-private storage.&lt;/P&gt;
&lt;P&gt;Henry&lt;/P&gt;</description>
      <pubDate>Sat, 03 Dec 2005 07:52:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959388#M5293</guid>
      <dc:creator>Henry_G_Intel</dc:creator>
      <dc:date>2005-12-03T07:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: KMP_MALLOC vs allocate</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959389#M5294</link>
      <description>&lt;DIV&gt;I refer not to stack allocate but rather to heap allocation from a heap local to the default processor for a thread. This applies to NUMA based systems where memory is distributed in multiple nodes and access is not uniform. See:&lt;/DIV&gt;
&lt;DIV&gt;&lt;A href="http://www.microsoft.com/whdc/system/platform/server/datacenter/numa_isv.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/system/platform/server/datacenter/numa_isv.mspx&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV&gt;for information on MUMA systems&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;Jim Dempsey&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 03 Dec 2005 12:10:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959389#M5294</guid>
      <dc:creator>jim_dempsey</dc:creator>
      <dc:date>2005-12-03T12:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: KMP_MALLOC vs allocate</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959390#M5295</link>
      <description>&lt;P&gt;Jim,&lt;/P&gt;
&lt;P&gt;As far as I know, the Intel 9.0 compiler does not generate NUMA-specific code. The Fortran 90 ALLOCATE intrinsic simply allocates memory from the global heap. I'll try to get someone from the compiler team to verify this.&lt;/P&gt;
&lt;P&gt;Henry&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 09 Dec 2005 06:16:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959390#M5295</guid>
      <dc:creator>Henry_G_Intel</dc:creator>
      <dc:date>2005-12-09T06:16:40Z</dc:date>
    </item>
    <item>
      <title>Re: KMP_MALLOC vs allocate</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959391#M5296</link>
      <description>&lt;P&gt;Thanks. When you refer the question include the following additional information.&lt;/P&gt;
&lt;P&gt;The platform is WinXP Pro SP2 but installed from my MSDN subscription. i.e. Installation was to WinXP, then Windows Updated (several times) until through SP2. Also modified BOOT.INI to inclued /PAE.&lt;/P&gt;
&lt;P&gt;I see no performance difference as I migratea pair ofthreads between processors on a 2-node NUMA system with 4 cores.&lt;/P&gt;
&lt;P&gt;I believe I have the system BIOS set to not interlieve the NUMA nodes. Maybe that isn't functioning on the system BIOS. Because if all the memory were allocated on one node then you would expect a performance change as the processing moved from one node to the other (while data remained in the node of allocation).&lt;/P&gt;
&lt;P&gt;I am trying to get the most out of the system.&lt;/P&gt;
&lt;P&gt;Jim Dempsey&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 09 Dec 2005 23:57:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/KMP-MALLOC-vs-allocate/m-p/959391#M5296</guid>
      <dc:creator>jim_dempsey</dc:creator>
      <dc:date>2005-12-09T23:57:54Z</dc:date>
    </item>
  </channel>
</rss>

