There are a few design specifications:
- Server Design Specification
- Storage Design Specification
- Data Center Design Specification
- Virtual IO Design Specification
- Hardware Management Specification
- Certification Standards
Linux Toolkits Blog is a scratch-pad of tips and findings on Linux
# ompi_info -a | grep 'Fort integer size'If the output is as below, you have to compile OpenMPI with 64 bits.
Fort integer size: 4
# ./configure --prefix=/usr/local/openmpi CXX=icpc CC=icc F77=ifort FC=ifort FFLAGS=-i8 FCFLAGS=-i8 # make -j 8 # make install
# ./configure --prefix=/usr/local/openmpi CXX=g++ CC=gcc F77=gfortran FC=gfortran \ FFLAGS="-m64 -fdefault-integer-8" \ CFLAGS="-m64 -fdefault-integer-8" \ CFLAGS=-m64 \ CXXFLAGS=-m64 # make -j 8 # make install
export $PATH=/usr/local/openmpi/bin:$PATH export $LD_LIBRARY_PATH=/usr/local/openmpi/lib:$LD_LIBRARY_PATH
# ompi_info -a | grep 'Fort integer size' Fort integer size: 8
WARNING: It appears that your OpenFabrics subsystem is configured to only
allow registering part of your physical memory. This can cause MPI jobs to
run with erratic performance, hang, and/or crash.
This may be caused by your OpenFabrics vendor limiting the amount of
physical memory that can be registered. You should investigate the
relevant Linux kernel module parameters that control how much physical
memory can be registered, and increase them to allow registering all
physical memory on your machine.
See this Open MPI FAQ item for more information on these Linux kernel module
parameters:
http://www.open-mpi.org/faq/?category=openfabrics#ib-locked-pages
Local host: node02
Registerable memory: 32768 MiB
Total memory: 65476 MiB
Your MPI job will continue, but may be behave poorly and/or hang.
The explanation solution can be found at How to increase MTT Size in Mellanox HCA.# bjobs -u all
# bjobs -p
# bjobs -lp
# bjobs -l 6653
# bjobs -s
# bpeek 12345
# bkill 12345
# bstop 12345
# bresume 12345
# getconf PAGESIZE 4096