<?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 The very basic distinction in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008735#M3871</link>
    <description>&lt;P&gt;The very basic distinction between the two is that the latter (fabric) is a component of the former (cluster).&amp;nbsp; At a very high level, an HPC cluster is a set of homogeneous machines connected together through some high-speed interconnect.&amp;nbsp; And even those definitions are now changing since the machines no longer have to be homogeneous - some might have coprocessor cards, others might not; they might be running different architectures, have different OS or resources available, etc.&lt;/P&gt;

&lt;P&gt;When we say fabric, we usually refer to the software-level layer that MPI, for example, might use to communicate between the nodes.&amp;nbsp; Underneath the fabric would be the low-level interconnect (e.g. ethernet, infiniband) and all its associated drivers.&lt;/P&gt;

&lt;P&gt;So if you start at highest application level, you as a developer will be making calls to the MPI library, the MPI library would be interacting with the underlying fabric interface (e.g. for Intel MPI, you would select the&amp;nbsp;'dapl' fabric to run over the infiniband network), which will in turn do its own communication to the firmware that sits on top of the network cards.&lt;/P&gt;

&lt;P&gt;I hope this helped a bit :)&amp;nbsp; Let me know if you have further questions.&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
	~Gergana&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jul 2015 23:39:11 GMT</pubDate>
    <dc:creator>Gergana_S_Intel</dc:creator>
    <dc:date>2015-07-13T23:39:11Z</dc:date>
    <item>
      <title>Cluster vs. Fabric</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008734#M3870</link>
      <description>&lt;P&gt;Hello !&lt;/P&gt;

&lt;P&gt;What is the difference between a cluster and a fabric? Is the network architecture the differentiating element?&lt;/P&gt;

&lt;P&gt;Many thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 19:22:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008734#M3870</guid>
      <dc:creator>octogone</dc:creator>
      <dc:date>2015-07-13T19:22:56Z</dc:date>
    </item>
    <item>
      <title>The very basic distinction</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008735#M3871</link>
      <description>&lt;P&gt;The very basic distinction between the two is that the latter (fabric) is a component of the former (cluster).&amp;nbsp; At a very high level, an HPC cluster is a set of homogeneous machines connected together through some high-speed interconnect.&amp;nbsp; And even those definitions are now changing since the machines no longer have to be homogeneous - some might have coprocessor cards, others might not; they might be running different architectures, have different OS or resources available, etc.&lt;/P&gt;

&lt;P&gt;When we say fabric, we usually refer to the software-level layer that MPI, for example, might use to communicate between the nodes.&amp;nbsp; Underneath the fabric would be the low-level interconnect (e.g. ethernet, infiniband) and all its associated drivers.&lt;/P&gt;

&lt;P&gt;So if you start at highest application level, you as a developer will be making calls to the MPI library, the MPI library would be interacting with the underlying fabric interface (e.g. for Intel MPI, you would select the&amp;nbsp;'dapl' fabric to run over the infiniband network), which will in turn do its own communication to the firmware that sits on top of the network cards.&lt;/P&gt;

&lt;P&gt;I hope this helped a bit :)&amp;nbsp; Let me know if you have further questions.&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
	~Gergana&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 23:39:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008735#M3871</guid>
      <dc:creator>Gergana_S_Intel</dc:creator>
      <dc:date>2015-07-13T23:39:11Z</dc:date>
    </item>
    <item>
      <title>what dose MPI &amp; HPC starnd</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008736#M3872</link>
      <description>&lt;P&gt;what dose MPI &amp;amp; HPC starnd for?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jul 2015 14:59:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008736#M3872</guid>
      <dc:creator>winura_w_</dc:creator>
      <dc:date>2015-07-14T14:59:05Z</dc:date>
    </item>
    <item>
      <title>MPI is the Message Passing</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008737#M3873</link>
      <description>&lt;P&gt;MPI is the &lt;A href="http://www.mcs.anl.gov/research/projects/mpi/"&gt;Message Passing Interface&lt;/A&gt; - a set of library routines that allows explicit communication between independent nodes.&lt;/P&gt;

&lt;P&gt;HPC is High Performance Computing - a field of technology using &lt;A href="https://en.wikipedia.org/wiki/Supercomputer"&gt;supercomputers&lt;/A&gt; to solve compute-intensive scientific and engineering problems.&lt;/P&gt;

&lt;P&gt;~Gergana&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jul 2015 19:05:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Cluster-vs-Fabric/m-p/1008737#M3873</guid>
      <dc:creator>Gergana_S_Intel</dc:creator>
      <dc:date>2015-07-14T19:05:44Z</dc:date>
    </item>
  </channel>
</rss>

