Problem Details:
OS Version: Linux
Product Version: any
Date: 08-Dec-05
Q. Will the Opteron and Intel SDKs (Basic and Enhanced ) run and
be supported on HP's Linux Opteron and Intel clusters?
A. Yes. These SDKs are designed to work and be supported on any
Linux (RHAT or SUSE) clusters made up of the AMD64 and the 64-bit Intel
Xeon processors.
index
|
Problem Details:
OS Version: Linux
Product Version: any
Date: 08-Dec-05
Q. Will HP-MPI work with the Absoft SDKs?
A. HP-MPI will work with existing Absoft SDKs on compatible platforms
if you decide to use it in place of the default MPI included with the
SDK.
index
|
Problem Details:
OS Version: Linux
Product Version: any
Date: 08-Dec-05
Q. Will Intel support Intel tools in SDKs which are run on Opteron?
A. Yes. The Intel Tools included are the Intel C/C++ and Fortran
Compilers as well as Intel MPI. We are currently shipping two SDKs for
Opteron. One is the Intel SDK for Opteron, the other is the Pathscale
SDK for Opteron based servers.
index
|
Problem Details:
OS Version: Linux
Product Version: any
Date: 08-Dec-05
Q. Why do Absoft's SDKs include compilers from multiple vendors?
A. Absoft compilers are included as a component of the standard
SDK to provide a source compatible compiler solution across multiple architectures/OSs.
As compatible as compilers are, there are often performance differences
by application and extra feature differences which you may want to exploit.
index
|
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. How do I enable VMX support with the IBM XL compilers?
A. VMX support only works on PPC970 POWER chips (Like the IBM
JS20) on SLES9 operating system. VMX support is not included in the
POWER4 or POWER5 chips. To enable VMX support type:
xlc -O3 -qarch=auto -qhot=simd
For MPI codes you can load the "lam-vmx" module to enable VMX support
for the MPI compilers If your hardware platform does not support VMX you
will get the following error message:
1506-1163 (W) Suboption simd of option hot is not supported
for the target architecture and is ignored.
If you are on RHEL3, which does not have ability to support VMX you will
get the following message
1506-1272 (W) Suboption simd of option hot is ignored
when option noenablevmx is specified.
index
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. How do I use RSH instead of SSH with the HPC SDK?
A. Load the module "lam-use-rsh". This will set the environment
variable LAMRSH to use "rsh" instead of "ssh -x". Next you will need to
use "savemodules" command to save this setting after loading this module
and before typing lamboot. Here is an example:
shellprompt% module load lam-use-rsh
shellprompt% savemodules
index
|
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. When I use mpirun it appears to hang.
A. Make sure that passwordless SSH is setup for your hosts that
you want to run LAM/MPI on. If you are using the file “machinefile”
as the argument to lamboot, you can test your configuration by typing
the following command:
recon machinefile
where machinefile is the name of the machinefile. Here is an example of
a successful test:
rwm@exaltation:~> recon machinefile
-----------------------------------------------------------------------------
Woo hoo!
recon has completed successfully. This means that you will most likely
be able to boot LAM successfully with the "lamboot" command (but this
is not a guarantee). See the lamboot(1) manual page for more
information on the lamboot command.
If you have problems booting LAM (with lamboot) even though recon
worked successfully, enable the "-d" option to lamboot to examine each
step of lamboot and see what fails. Most situations where recon
succeeds and lamboot fails have to do with the hboot(1) command (that
lamboot invokes on each host in the hostfile).
-----------------------------------------------------------------------------
If you get any other output, you need to contact your systems administrator
to assist you in setting up passwordless ssh between the nodes listed
in your machinefile before typing lamboot.
index
|
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. Is an optimized BLAS included in the Power/Linux ESSL?
A. Yes BLAS routines are provided by ESSL 4.2. The complete list
of BLAS routines can be found in Appendix A of the ESSL 4.2 reference
guide.
The ESSL 4.2 reference guide for Linux on Power 4.2 is freely downloadable
from this URL:
http://publib.boulder.ibm.com/clresctr/windows/public/esslbooks.html#essl_42_linux
index
|
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. Is a full list of LAPACK routines included in the Power/Linux
ESSL available?
A. Yes LAPACK routines are provided by ESSL 4.2. The complete
list of LAPACK routines can be found listed in Appendix B of the ESSL
4.2 reference guide.
The ESSL 4.2 reference guide for Linux on Power 4.2 is freely downloadable
from this URL:
http://publib.boulder.ibm.com/clresctr/windows/public/esslbooks.html#essl_42_linux
index
|
|
Platform: Linux on Power
Problem Details:
OS Version: SLES 9, RHEL 3
Product Version: any
Date: 07-Dec-04
Q. When I do a “module switch ibm-xl-compilers absoft-compilers”
why does mpicc -showme still show the IBM XL compilers
being used?
A. The compiler switching commands do not change which compilers
LAM/MPI uses, only the compilers in your PATH. To switch which underlying
compiler LAM/MPI uses run the command:
module switch lam-32bit-7.1 lam-absoft-32bit-7.1
index
|