<?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 Hand-picking DAPL providers in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Hand-picking-DAPL-providers/m-p/1055136#M51504</link>
    <description>&lt;P&gt;Is there a way to set a specific DAPL provider individually for each host in the machine file? This seems particularly important with native Xeon Phi applications, as MPI does not choose the optimal provider automatically (at least with two cards per host).&lt;/P&gt;</description>
    <pubDate>Thu, 13 Nov 2014 14:35:35 GMT</pubDate>
    <dc:creator>Andrey_Vladimirov</dc:creator>
    <dc:date>2014-11-13T14:35:35Z</dc:date>
    <item>
      <title>Hand-picking DAPL providers</title>
      <link>https://community.intel.com/t5/Software-Archive/Hand-picking-DAPL-providers/m-p/1055136#M51504</link>
      <description>&lt;P&gt;Is there a way to set a specific DAPL provider individually for each host in the machine file? This seems particularly important with native Xeon Phi applications, as MPI does not choose the optimal provider automatically (at least with two cards per host).&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2014 14:35:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Hand-picking-DAPL-providers/m-p/1055136#M51504</guid>
      <dc:creator>Andrey_Vladimirov</dc:creator>
      <dc:date>2014-11-13T14:35:35Z</dc:date>
    </item>
  </channel>
</rss>

