On Mar 11, 2005, at 10:22 PM, karla b wrote:
> Sincere apologies to all for length of previous mail, as explained to
> Anthony, I was attempting to give a full (it seems far to complete)
> description of exactly what the problem being solved and this smaller
> model is supposed to do.
>
> Some very kind suggestions from Anthony regarding the use of non
> blocking communications have resulted in this newer version, please
> find attached.
>
> I am not completely sure of how to implement this new MPI_Waitany
> functionality and so have left commented out the final sending of
> "Dietags".
>
> Apologies to all experienced users in advance for what would be deemed
> novice errors, the paradigm is new.
So what exactly is the problem you are seeing? We (the LAM developers)
unfortunately can not provide general debugging assistance - there are
too many users and not nearly enough developers. That being said,
we're more than willing to answer specific questions you might have
about MPI and specifically about the LAM implementation.
I do see a couple of problems with your code that seem to indicate a
misunderstanding of the MPI send/recv interfaces. You might want to
find a good resource on using MPI and work through the examples. One I
would suggest is the NCSA's Introduction to MPI:
http://webct.ncsa.uiuc.edu:8900/public/MPI/
In particular, in the client you have an MPI_Waitany at the top of a
while(1) loop, but only post a non-blocking operation outside of the
while() loop. This might work the first time through the loop, but
after that, you might not have any requests that can be progressed to
completion. You also don't call any Test or Wait functions for the
non-blocking communication used in the master, so the communication may
never complete there.
Hope this helps,
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have an LAM/MPI day: http://www.lam-mpi.org/
|
