ode ? (the node distribution could be given in the
"machinefile" file, as with LAM MPI)
The code (Fortran 90) of this example and makefile is attached as a tar
file.
Thank you very much
Jean Latour
spawn+connect.tar.gz
Description: Binary data
<>
e from the beginning as in
your example.
Do you know if this specific feature will be implemented in Open-MPI (I
hope it will be),
and possibly when ?
Dynamic applications really need this.
Best Regards,
Jean Latour
Edgar Gabriel wrote:
so for my tests, Open MPI did follow the machinefile (
slave3 and slave4 disconnect from master an finalize
11) master finalize
Hope it helps
Best regards,
Jean Latour
Ralph Castain wrote:
We expect to have much better support for the entire comm_spawn
process in the next incarnation of the RTE. I don't expect that to be
included in a release, how
) Is it possible to use specific IB drivers for optimal performance ?
(should reach almost 800 MB/sec)
Thank you very much for your help
Best Regards,
Jean Latour
<>
mvapich on the same network.
Since we do NOT have a PCI-X hardware, I believe this is the maximum we
can get from the
hardware.
Thanks a lot for your explanations for this tunning of OpenMPI
Best Regards,
Jean
George Bosilca wrote:
On Thu, 16 Mar 2006, Jean Latour wrote:
My questions are
Hello,
It seems to me there is only one way to create a communication between
two MPI_COMM_WORLD : use MPI_Open_Port with a specific
IP + port address, and then MPI_comm_connect / MPI_comm_accept.
In order to ease the port number communication, the use of MPI_publish-name
/ MPI_lookup_name is a
