<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Jeff,<div class=""><br class=""></div><div class="">I wrote some notes about our discussion.</div><div class=""><a href="https://github.com/mpiwg-p2p/p2p-issues/wiki/notes-2017-03-27" class="">https://github.com/mpiwg-p2p/p2p-issues/wiki/notes-2017-03-27</a></div><div class=""><br class=""></div><div class="">In short, the memory must be returned to the original owner for de-allocation.</div><div class="">We mentioned an attach/detach method for using user memory.</div><div class="">We also discussed using Fsend/Arecv to/from MPI_COMM_NULL to transfer ownership without needing another message.</div><div class="">This needs careful thought - hence the suggestion for sequence diagrams.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Dan.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 27 Mar 2017, at 22:42, Jeff Hammond <<a href="mailto:jeff.science@gmail.com" class="">jeff.science@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Actually, it has to be required in the literal sense.</div><div class=""><br class=""></div><div class="">Fsend frees memory. Has to know which allocator used. MPI_Alloc_mem is the only one MPI knows about. </div><div class=""><br class=""></div><div class="">Same in reverse for Arecv and MPI_Free_mem.</div><div class=""><br class=""></div><div class="">How else can you do it? We could register callbacks for memory allocator but that will almost certainly prevent every useful optimization. </div><div class=""><br class=""></div><div class="">Jeff<br class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On Mar 27, 2017, at 8:57 AM, Dan Holmes <<a href="mailto:d.holmes@epcc.ed.ac.uk" class="">d.holmes@epcc.ed.ac.uk</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class="">“required” is possibly too strong. “advisable” would be closer to my expectation. “needed in order for MPI to enable all possible optimisations” is more wordy/precise.<div class=""><br class=""></div><div class="">Cheers,</div><div class="">Dan.<br class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 27 Mar 2017, at 16:55, Jeff Hammond <<a href="mailto:jeff.science@gmail.com" class="">jeff.science@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">No. MPI_Alloc_mem and MPI_Free_mem were going to be required. At least that was my plan. <br class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On Mar 27, 2017, at 8:51 AM, Jim Dinan <<a href="mailto:james.dinan@gmail.com" class="">james.dinan@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Did we previously look at using MPI_Buffer_attach as a way to support allocate-and-recv?</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Mar 27, 2017 at 11:38 AM, Jeff Hammond <span dir="ltr" class=""><<a href="mailto:jeff.science@gmail.com" target="_blank" class="">jeff.science@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm on vacation but I endorse other people doing stuff with Fsend-Arecv, since the slacker who owned it for the past two years hasn't made any progress. I think I copied all the relevant content to GitHub already.<br class="">
<br class="">
Jeff<br class="">
<br class="">
Sent from my iPhone<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
> On Mar 27, 2017, at 8:16 AM, Dan Holmes <<a href="mailto:d.holmes@epcc.ed.ac.uk" class="">d.holmes@epcc.ed.ac.uk</a>> wrote:<br class="">
><br class="">
> Hi Jim, et al,<br class="">
><br class="">
> I was hoping to move the WG on to talking about Freeing-Send and Allocating-Receive (Fsend & Arecv).<br class="">
><br class="">
> I’d like to re-boot and refresh caches on that with a goal of presenting something (probably informally) next face-to-face meeting in June.<br class="">
><br class="">
> I’ll start the call and see how many turn up.<br class="">
><br class="">
> Cheers,<br class="">
> Dan.<br class="">
><br class="">
>> On 27 Mar 2017, at 15:28, Jim Dinan <<a href="mailto:james.dinan@gmail.com" class="">james.dinan@gmail.com</a>> wrote:<br class="">
>><br class="">
>> Hi All,<br class="">
>><br class="">
>> The info query proposal seems to be converging. I don't think there's anything to discuss on this topic this week.<br class="">
>><br class="">
>> Current status is that Pavan will check with vendors to make sure they are ok with updating MPICH to report the user's info key value instead of the effective value being used by the implementation. Assuming this is ok, it sounds like the proposal that was read at the last meeting is ready to move forward into voting.<br class="">
>><br class="">
>> Are there any other topics for discussion? If not, I think we can cancel today's meeting.<br class="">
>><br class="">
>> Cheers,<br class="">
>> ~Jim.<br class="">
>> ______________________________<wbr class="">_________________<br class="">
>> mpiwg-p2p mailing list<br class="">
>> <a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a><br class="">
>> <a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank" class="">https://lists.mpi-forum.org/<wbr class="">mailman/listinfo/mpiwg-p2p</a><br class="">
><br class="">
><br class="">
> --<br class="">
> The University of Edinburgh is a charitable body, registered in<br class="">
> Scotland, with registration number SC005336.<br class="">
><br class="">
> ______________________________<wbr class="">_________________<br class="">
> mpiwg-p2p mailing list<br class="">
> <a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a><br class="">
> <a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank" class="">https://lists.mpi-forum.org/<wbr class="">mailman/listinfo/mpiwg-p2p</a><br class="">
______________________________<wbr class="">_________________<br class="">
mpiwg-p2p mailing list<br class="">
<a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a><br class="">
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank" class="">https://lists.mpi-forum.org/<wbr class="">mailman/listinfo/mpiwg-p2p</a></div></div></blockquote></div><br class=""></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">mpiwg-p2p mailing list</span><br class=""><span class=""><a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a></span><br class=""><span class=""><a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</a></span></div></blockquote></div>_______________________________________________<br class="">mpiwg-p2p mailing list<br class=""><a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a><br class=""><a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</a></div></blockquote></div><br class=""></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">The University of Edinburgh is a charitable body, registered in</span><br class=""><span class="">Scotland, with registration number SC005336.</span><br class=""></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">mpiwg-p2p mailing list</span><br class=""><span class=""><a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a></span><br class=""><span class=""><a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</a></span></div></blockquote></div>_______________________________________________<br class="">mpiwg-p2p mailing list<br class=""><a href="mailto:mpiwg-p2p@lists.mpi-forum.org" class="">mpiwg-p2p@lists.mpi-forum.org</a><br class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</div></blockquote></div><br class=""></div></body></html>