[openib-general] openMPI for 2.6.17.10 kernel

[david elsen]

oops, sorry, my fault. I will try it again.

Shaun Rowland <rowland at cse.ohio-state.edu> wrote: david elsen wrote:
> Shaun,
> 
> I tried this and am getting some error messages:
> 
> Please see following:
> [root at ammasso2 osu_benchmarks]# mpicc osu_latency.c
> [root at ammasso2 osu_benchmarks]# ls
> a.out              osu_bw.c           osu_latency.c     osu_put_bw.c
> osu_acc_latency.c  osu_get_bw.c       osu_latency_mt.c  osu_put_latency.c
> osu_bibw.c         osu_get_latency.c  osu_put_bibw.c
> [root at ammasso2 osu_benchmarks]# ./a.out

You need to execute these with mpiexec after starting mpdboot, so the
process would be something like:

mpicc -o osu_lat osu_latency.c
mpdboot -n 2 -f hosts
mpiexec -n 2 ./osu_lat
....
mpdallexit

As detailed in the User Guide:

http://nowlab.cse.ohio-state.edu/projects/mpi-iba/download-mvapich2/mvapich2_user_guide.html#x1-170005.2

You should also see this section of the User Guide if you have problems
with iWARP:

http://nowlab.cse.ohio-state.edu/projects/mpi-iba/download-mvapich2/mvapich2_user_guide.html#x1-400007.3

Also, this section describes using iWARP with MVAPICH2:

http://nowlab.cse.ohio-state.edu/projects/mpi-iba/download-mvapich2/mvapich2_user_guide.html#x1-230005.8

Have you set up everything (like /etc/mv2.conf)? Are you using
the environment variable MV2_USE_RDMA_CM as described above? With the
mpiexec command, it should be enough to export this variable to a value
of 1 in the same environment in which you execute mpiexec - this will
automatically propagate to the processes on remote machines.
-- 
Shaun Rowland rowland at cse.ohio-state.edu
http://www.cse.ohio-state.edu/~rowland/


 
---------------------------------
Any questions?  Get answers on any topic at Yahoo! Answers. Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20061206/e21b463f/attachment.html>