This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
I think ultimately it would comes down to whether code execution is
more important than receiving the message in a timely fashion.
On 2/2/11, amjad ali <amjad11_at_[hidden]> wrote:
> Perhaps often it is more useful to use MPI_WAIT rather than MPI_TEST type
> fucntions, because at MPI_WAIT point it will be taken care of communication
> completion, automatically, which may be necessary before going ahead. with
> MPI_TEST it would become the responsibility of the programmer to handle the
> situation if the test is FALSE/FAILED.
> On Wed, Feb 2, 2011 at 7:50 AM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
>> Yes; you can use any of the various flavors of the MPI_TEST* functions.
>> On Feb 2, 2011, at 7:03 AM, Bibrak Qamar wrote:
>> > Hello All,
>> > Is there any way to find whether a non blocking communication has
>> finished without calling the wait( ) function.
>> > Thanks
>> > Bibrak Qamar
>> > Undergraduate Student BIT-9
>> > Member Center for High Performance Scientific Computing
>> > NUST-School of Electrical Engineering and Computer Science.
>> > _______________________________________________
>> > users mailing list
>> > users_at_[hidden]
>> > http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Jeff Squyres
>> For corporate legal information go to:
>> users mailing list
Sent from my mobile device
University of California, San Diego