<?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 Dual Rail Performance in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781343#M384</link>
    <description>By default Intel MPI uses shm:dapl fabric.&lt;BR /&gt;To enable OFA fabric you need to either set environment variable I_MPI_FABRICS=shm:ofa or add an option '-genv I_MPI_FABRICS shm:ofa' to your mpirun command.&lt;BR /&gt;&lt;BR /&gt;Multi-rail feature is available with ofa fabric only and only with versions 4.0.x&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry</description>
    <pubDate>Fri, 30 Mar 2012 09:37:35 GMT</pubDate>
    <dc:creator>Dmitry_K_Intel2</dc:creator>
    <dc:date>2012-03-30T09:37:35Z</dc:date>
    <item>
      <title>Dual Rail Performance</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781339#M380</link>
      <description>Hello,&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;I have a dual rail FDR system with SandyBridge nodes. I have 16 processes assigned to each of four nodes and I am testing the all-to-all. I have enabled dual rail with&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;	export I_MPI_OFA_NUM_ADAPTERS=2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;	export I_MPI_OFA_RAIL_SCHEDULER=ROUND_ROBIN&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The ibstat shows&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;CA 'mlx4_0'&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;CA type: MT4099&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Number of ports: 1&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Firmware version: 2.10.2370&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Hardware version: 0&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Node GUID: 0x001e6703003dd888&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;System image GUID: 0x001e6703003dd88b&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Port 1:&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;State: Active&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Physical state: LinkUp&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Rate: 56&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Base lid: 78&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;LMC: 0&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;SM lid: 3&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Capability mask: 0x02514868&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Port GUID: 0x001e6703003dd889&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Link layer: InfiniBand&lt;/DIV&gt;&lt;DIV&gt;CA 'mlx4_1'&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;CA type: MT4099&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Number of ports: 1&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Firmware version: 2.10.700&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Hardware version: 0&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Node GUID: 0x0002c90300333e90&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;System image GUID: 0x0002c90300333e93&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;	&lt;/SPAN&gt;Port 1:&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;State: Active&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Physical state: LinkUp&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Rate: 56&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Base lid: 779&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;LMC: 0&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;SM lid: 618&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Capability mask: 0x02514868&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Port GUID: 0x0002c90300333e91&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="white-space: pre;"&gt;		&lt;/SPAN&gt;Link layer: InfiniBand&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Where does Intel MPI pick up the name of the adapters to use for dual rail mode?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;David Race&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 Mar 2012 15:04:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781339#M380</guid>
      <dc:creator>David_Race</dc:creator>
      <dc:date>2012-03-29T15:04:17Z</dc:date>
    </item>
    <item>
      <title>Dual Rail Performance</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781340#M381</link>
      <description>Hi David,&lt;BR /&gt;Intel MPI calls an IB verbs function to get a list of available IB devices. So, Intel MPI doesn't work with names of the adapters and doesn't try to read any configuration file. It should be done bylibibvers library.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Mar 2012 15:25:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781340#M381</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2012-03-29T15:25:16Z</dc:date>
    </item>
    <item>
      <title>Dual Rail Performance</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781341#M382</link>
      <description>I set I_MPI_DEBUG=10, then received&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;[16] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[16] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[28] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[28] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[32] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[32] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[35] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[35] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[36] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[36] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[37] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[37] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[38] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[40] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[40] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[41] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[41] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[42] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[42] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[43] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[43] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[48] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;[48] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;[16] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[16] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[28] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[28] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[32] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[32] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[35] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[35] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[36] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[36] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[37] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[37] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[38] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[40] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[40] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[41] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[41] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[42] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[42] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[43] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[43] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.2[48] DAPL startup(): trying to open default DAPL provider from dat registry: ofa-v2-mlx4_0-1[48] I_MPI_dlopen_dat(): trying to load default dat library: libdat2.so.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;From this an the Intel MPI Documentation, does this mean I need an entry for ofa-v2-mlx4_1-1 in the /etc/dat.conf file?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;I only have an entry for the first IB devices in the /etc/dat.conf file.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Is this correct?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;David&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 Mar 2012 17:01:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781341#M382</guid>
      <dc:creator>David_Race</dc:creator>
      <dc:date>2012-03-29T17:01:27Z</dc:date>
    </item>
    <item>
      <title>Dual Rail Performance</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781342#M383</link>
      <description>Hi David,&lt;BR /&gt;&lt;BR /&gt;afaik, you cannot use dapl for multirail. You'll have to use the shm:ofa fabric instead.&lt;BR /&gt;&lt;BR /&gt;cheers.</description>
      <pubDate>Fri, 30 Mar 2012 09:12:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781342#M383</guid>
      <dc:creator>karl_lehnberger</dc:creator>
      <dc:date>2012-03-30T09:12:45Z</dc:date>
    </item>
    <item>
      <title>Dual Rail Performance</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781343#M384</link>
      <description>By default Intel MPI uses shm:dapl fabric.&lt;BR /&gt;To enable OFA fabric you need to either set environment variable I_MPI_FABRICS=shm:ofa or add an option '-genv I_MPI_FABRICS shm:ofa' to your mpirun command.&lt;BR /&gt;&lt;BR /&gt;Multi-rail feature is available with ofa fabric only and only with versions 4.0.x&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt; Dmitry</description>
      <pubDate>Fri, 30 Mar 2012 09:37:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Dual-Rail-Performance/m-p/781343#M384</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2012-03-30T09:37:35Z</dc:date>
    </item>
  </channel>
</rss>

