Build on a machine without a Xeon Phi card?

[Todd_A_Intel]

It seems that some portion of the MPSS is required for building an application and additional parts are required for the machine to communicate with the card in order to actually use it.  Is there a way to just install the portion of the MPSS package necessary for building on say a Fedora system and then transfer the binary to a system with a Xeon Phi card and the full MPSS?

[Frances_R_Intel]

I've never tried this myself, but -

Support for the Intel Xeon Phi coprocessors is built into the Intel compilers themselves. If you are using the Intel compilers (which will give you the best performance on the coprocessor), that should be all you need to compile. You will get error messages when you try to link the code, because not all the libraries will be there but you should be able to resolve those when you move the code back.

If you need to use the GNU compilers, you can find a cross compiler in the MPSS package, gpl/package-cross-k1om.tar.bz2. 

[Todd_A_Intel]

Frances Roth (Intel) wrote:

I've never tried this myself, but -

Support for the Intel Xeon Phi coprocessors is built into the Intel compilers themselves. If you are using the Intel compilers (which will give you the best performance on the coprocessor), that should be all you need to compile. You will get error messages when you try to link the code, because not all the libraries will be there but you should be able to resolve those when you move the code back.

If you need to use the GNU compilers, you can find a cross compiler in the MPSS package, gpl/package-cross-k1om.tar.bz2. 

When I tried a compile (not a link), it said "icc: warning #10362: Environment configuration problem encountered.  Please check for proper MPSS installation and environment setup."  Then "icc: error #10001: could not find directory in which the set of libstdc++ include files resides."

[attila_afra]

All you need to do is to extract the linux-k1om-4.7 folder from the intel-mic-gpl-*.rpm package into /usr. You might also need the SCIF includes and libs from that package.

[TimP]

If you have registered your license, on https://registrationcenter.intel.com under Cluster Studio for linux, you will find the add-on MPSS package for linking to Intel® Xeon Phi™ for the purpose mentioned at the top of this thread.

[Todd_A_Intel]

TimP (Intel) wrote:

If you have registered your license, on https://registrationcenter.intel.com under Cluster Studio for linux, you will find the add-on MPSS package for linking to Intel® Xeon Phi™ for the purpose mentioned at the top of this thread.

Did you mean to suggest that there is some different package other than the regular KNC...tgz ones that just has what you need for compile/link and not the driver for communicating with the card? 

[Todd_A_Intel]

attila.afra wrote:

All you need to do is to extract the linux-k1om-4.7 folder from the intel-mic-gpl-*.rpm package into /usr. You might also need the SCIF includes and libs from that package.

I tried it and I can confirm that this approach seems to work.  Thanks!

[TimP]

The components available on registrationcenter ought to be the same as you would extract from the full k10m installation component folder.

[kamaxi_r_]

Good information is provided and You will get error messages when you try to link the code.

[wnag_y_]

AMD's new Tahiti based FirePro S10000 sports a little more than just a GPU upgrade it sports two GPU updates as this is a dual GPU card.  According to The Register it should run about $3,600 and need 375W to perform, numbers which make it a more efficient card than the S9000 even though it needs significantly more Support Bars cash and power to run.  It is a 2 slot card, a necessity in the server and workstation world and while it does not support CrossFire it does support EyeFinity with its DVI port and four Mini DisplayPorts.

[Chris_Samuel]

Here are the RPMs we have installed on our HPC login node (RHEL6) without a MIC for successful compilation.

[root@barcoo ~]# rpm -qa | egrep 'mpss|intel' | fgrep -vw x11 
mpss-coi-dev-3.1.2-1.glibc2.12.2.x86_64
mpss-metadata-3.1.2-1.glibc2.12.2.x86_64
intel-composerxe-compat-k1om-3.1.2-1.x86_64
mpss-coi-3.1.2-1.glibc2.12.2.x86_64
mpss-modules-headers-dev-3.1.2-1.glibc2.12.2.x86_64
mpss-sdk-k1om-3.1.2-1.x86_64
mpss-modules-headers-3.1.2-1.glibc2.12.2.x86_64
mpss-eclipse-cdt-mpm-3.1.2-1.glibc2.12.2.x86_64
mpss-metadata-dev-3.1.2-1.glibc2.12.2.x86_64

Hope they help!