Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| difx:nativemk5 [2011/12/09 02:37] – walterbrisken | difx:nativemk5 [2012/04/02 22:02] – [4. Compilation of ''mpifxcorr''] adamdeller |
|---|
| ==== 1. Linux requirements ==== | ==== 1. Linux requirements ==== |
| |
| Compatibility of the Conduant StreamStor drivers severely limits the choice of Linux kernels. The supported kernel versions depend on the exact version of the driver (the SDK version number) that is used. SDK version 8.2 or later are suggested as earlier versions have known stability issues related to the way the StreamStor cards are accessed by DiFX. As of this writing (Dec 8, 2011) only 32-bit kernels are supported. See [[mixingarchitectures|mixing architectures]] to see how to configure a cluster to support a mixture of 32 bit and 64 bit members of a cluster running ''mpifxcorr''. Note that mixing different StreamStor SDK versions across the cluster is possible, but for each a separately compiled version of the ''mpifxcorr'' binary will be required due to differences in library requirements. Differences between major SDK releases (e.g., SDK8 and SDK9) usually also have API-level changes. Currently ''mpifxcorr'' can be compiled against either SDK8 or SDK9 series. There are reports (from RJC) that Linux Kernel versions greater than 2.6.18 interact badly with the StreamStor/Jungo driver, resulting in garbage data returned for read sizes greater than 8 MB. | Compatibility of the Conduant StreamStor drivers severely limits the choice of Linux kernels. The supported kernel versions depend on the exact version of the driver (the SDK version number) that is used. SDK version 8.2 or later are suggested as earlier versions have known stability issues related to the way the StreamStor cards are accessed by DiFX. As of this writing (Dec 8, 2011) only 32-bit kernels are supported. See [[mixingarchitectures|mixing architectures]] to see how to configure a cluster to support a mixture of 32 bit and 64 bit members of a cluster running ''mpifxcorr''. Note that mixing different StreamStor SDK versions across the cluster is possible, but for each a separately compiled version of the ''mpifxcorr'' binary will be required due to differences in library requirements. Differences between major SDK releases (e.g., SDK8 and SDK9) usually also have API-level changes. Currently ''mpifxcorr'' can be compiled against either SDK8 or SDK9 series. There are reports (from RJC: specific failure is on kernel 2.6.26 and SDK 9.0) that Linux Kernel versions greater than 2.6.18 interact badly with the StreamStor/Jungo driver, resulting in garbage data returned for read sizes greater than 8 MB. |
| |
| ==== 2. Installation of Conduant's streamstor Software Development Kit (SDK) ==== | ==== 2. Installation of Conduant's streamstor Software Development Kit (SDK) ==== |
| ==== 4. Compilation of ''mpifxcorr'' ==== | ==== 4. Compilation of ''mpifxcorr'' ==== |
| |
| Compilation of ''mpifxcorr'' should proceed as usual. The configuration process should find the streamstor.pc file and properly configure the compilation for native mark5. You should see ''nativemk5.cpp'' being correlated as a result. | Compilation of ''mpifxcorr'' should proceed as usual. The configuration process should find the streamstor.pc file and properly configure the compilation for native mark5. You should see ''nativemk5.cpp'' being compiled as a result. |
| |
| ==== 5. Dealing with Mark5 Module directories ==== | ==== 5. Dealing with Mark5 Module directories ==== |
