[mpich-discuss] How to use non-blocking send/receive without calling MPI_Wait

[Balaji, Pavan]

MPI_REQUEST_FREE.  Please read the remaining emails on this thread.

  -- Pavan

> On Apr 3, 2015, at 7:56 PM, Lei Shi <lshi at ku.edu> wrote:
> 
> Sorry. I just take a quick look of that slides this afternoon. Got the details now. 
> 
> So can I make a quick conclusion that there is no way to avoid MPI_Wait or MPI_test with non-blocking send/receive. Even I don't care I have received the message or not. 
> 
> 
> On Fri, Apr 3, 2015 at 5:23 PM, Jeff Squyres (jsquyres) <jsquyres at cisco.com> wrote:
> On Apr 3, 2015, at 6:09 PM, Balaji, Pavan <balaji at anl.gov> wrote:
> >
> > I didn't look through the video, but what you are saying is not true.  You can free the request in the application (this simply reduces the reference count to that request).  MPI will still maintain one reference count to the request and will only free it when the data transfer completes.
> 
> That's correct.  The point of that blog entry is that you have to tell MPI that you're done with a request somehow, otherwise MPI *has* to keep those resources allocated.
> 
> MPI_TEST*/MPI_WAIT* are the usual ways to do this.  MPI_REQUEST_FREE is also a valid method, but, as has been stated, isn't advisable.
> 
> --
> Jeff Squyres
> jsquyres at cisco.com
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> 

--
Pavan Balaji  ✉️
http://www.mcs.anl.gov/~balaji

_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss