Difference between revisions of "OpenMPI"
From HCL
Zhongziming (talk | contribs) |
(→MCA parameter files) |
||
| Line 6: | Line 6: | ||
cat $HOME/.openmpi/mca-params.conf | cat $HOME/.openmpi/mca-params.conf | ||
btl_tcp_if_exclude = lo,eth1 | 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 == | == Running applications on Multiprocessors/Multicores == | ||
Latest revision as of 10:45, 22 August 2012
Contents
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
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.
