Difference between revisions of "OpenMPI"

Latest revision as of 11:45, 22 August 2012

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

This trick avoids a confirmation message asking "yes" when asked by SSH if a host should be added to known_hosts:

   ssh -q -o StrictHostKeyChecking=no

So with OpenMPI it can be used as

   mpirun --mca plm_rsh_agent "ssh -q -o StrictHostKeyChecking=no"

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

@@ Line 6: / Line 6: @@
   cat $HOME/.openmpi/mca-params.conf
   btl_tcp_if_exclude = lo,eth1
+== Handling SSH key issues ==
+This trick avoids a confirmation message asking "yes" when asked by SSH if a host should be added to known_hosts:
+    ssh -q -o StrictHostKeyChecking=no
+So with OpenMPI it can be used as
+    mpirun --mca plm_rsh_agent "ssh -q -o StrictHostKeyChecking=no"
 == Running applications on Multiprocessors/Multicores ==
 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#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 (eg:gdb)]
+== PERUSE ==
-** 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.
+[[Media:current_peruse_spec.pdf|PERUSE Specification]]
-** 2. Use mpirun to launch xterms (or equivalent) with serial debuggers.<br />  shell$ mpirun -np 4 xterm -e gdb my_mpi_application