From: Rick K. <rk...@nc...> - 2005-12-07 04:35:32
|
Giuseppe, There is one other thing I forgot to mention here: > /usr/local/mpich-1.2.7/bin/mpirun -np 2 /usr/local/bin/psrun cpi-mpi If this option still doesn't work for you, it might be that the MPI implementation is changing the command-line arguments supplied to psrun when the MPI program actually starts on the remote nodes. This would be the case, for example, if you are using the "ch_p4" version of MPICH as supplied by Argonne. What is happening there is that psrun isn't actually seeing the command "cpi-mpi", but something else altogether that is put back in order by the MPI routine MPI_Init. However, that is too late for psrun to be able to do its work. The only workarounds available for this problem are: 1. link the MPI application with the PMPI version of PerfSuite's libpshwpc library, which is built if you supplied the configure-time option --enable-mpi. The library is called "libpshwpc_mpi" and will be installed in the standard PerfSuite library directory. 2. Insert calls to libpshwpc in the MPI application itself. Both of these workarounds eliminate the need for using psrun altogether, so you should omit psrun in your mpirun command line if you use them. This topic was discussed some months back in this mailing list but I thought it would be helpful to recap. Thanks, Rick |