Difference between revisions of "OpenMPI"

From HCL
Jump to: navigation, search
(PERUSE)
Line 10: Line 10:
 
Process can be bound to specific sockets and cores on nodes by choosing right options of mpirun.
 
Process can be bound to specific sockets and cores on nodes by choosing right options of mpirun.
 
* [http://www.open-mpi.org/doc/v1.4/man1/mpirun.1.php#sect9 Process binding]
 
* [http://www.open-mpi.org/doc/v1.4/man1/mpirun.1.php#sect9 Process binding]
* [http://www.open-mpi.org/doc/v1.4/man1/mpirun.1.php#sect10 Rankfiles]
+
* [http://www.open-mpi.org/doc/v1.4/man1/mpirun.1.php#sect10 Rankfile]
 
 
== Debugging applications on Multiprocessors/Multicores ==
 
 
 
* [http://www.open-mpi.org/faq/?category=debugging#serial-debuggers Serial Debugger (Gdb)]
 
** 1. Attach to individual MPI processes after they are running.<br />  For example, launch your MPI application as normal with mpirun. Then login to the node(s) where your application is running and use the --pid option to gdb to attach to your application.
 
** 2. Use mpirun to launch xterms (or equivalent) with serial debuggers.
 
      shell$ mpirun -np 4 xterm -e gdb my_mpi_application
 
 
 
* [http://www.open-mpi.org/faq/?category=debugging#parallel-debuggers Parallel Debugers]
 
** [http://www.open-mpi.org/faq/?category=running#run-with-tv TotalView]
 
** [http://www.open-mpi.org/faq/?category=running#run-with-ddt DDT]
 
 
 
  
 
== PERUSE ==
 
== PERUSE ==
 
[[Media:current_peruse_spec.pdf|PERUSE Specification]]
 
[[Media:current_peruse_spec.pdf|PERUSE Specification]]

Revision as of 11:05, 12 July 2012

http://www.open-mpi.org/faq/

MCA parameter files

If you want to permanently use some MCA parameter settings, you can create a file $HOME/.openmpi/mca-params.conf, e.g.:

cat $HOME/.openmpi/mca-params.conf
btl_tcp_if_exclude = lo,eth1

Running applications on Multiprocessors/Multicores

Process can be bound to specific sockets and cores on nodes by choosing right options of mpirun.

PERUSE

PERUSE Specification