<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>No. MPI_Alloc_mem and MPI_Free_mem were going to be required. At least that was my plan. <br><br>Sent from my iPhone</div><div><br>On Mar 27, 2017, at 8:51 AM, Jim Dinan <<a href="mailto:james.dinan@gmail.com">james.dinan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Did we previously look at using MPI_Buffer_attach as a way to support allocate-and-recv?</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 27, 2017 at 11:38 AM, Jeff Hammond <span dir="ltr"><<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a>></span> wrote:<br><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>
<br>
Jeff<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br>
> On Mar 27, 2017, at 8:16 AM, Dan Holmes <<a href="mailto:d.holmes@epcc.ed.ac.uk">d.holmes@epcc.ed.ac.uk</a>> wrote:<br>
><br>
> Hi Jim, et al,<br>
><br>
> I was hoping to move the WG on to talking about Freeing-Send and Allocating-Receive (Fsend & Arecv).<br>
><br>
> 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>
><br>
> I’ll start the call and see how many turn up.<br>
><br>
> Cheers,<br>
> Dan.<br>
><br>
>> On 27 Mar 2017, at 15:28, Jim Dinan <<a href="mailto:james.dinan@gmail.com">james.dinan@gmail.com</a>> wrote:<br>
>><br>
>> Hi All,<br>
>><br>
>> The info query proposal seems to be converging. I don't think there's anything to discuss on this topic this week.<br>
>><br>
>> 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>
>><br>
>> Are there any other topics for discussion? If not, I think we can cancel today's meeting.<br>
>><br>
>> Cheers,<br>
>> ~Jim.<br>
>> ______________________________<wbr>_________________<br>
>> mpiwg-p2p mailing list<br>
>> <a href="mailto:mpiwg-p2p@lists.mpi-forum.org">mpiwg-p2p@lists.mpi-forum.org</a><br>
>> <a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/<wbr>mailman/listinfo/mpiwg-p2p</a><br>
><br>
><br>
> --<br>
> The University of Edinburgh is a charitable body, registered in<br>
> Scotland, with registration number SC005336.<br>
><br>
> ______________________________<wbr>_________________<br>
> mpiwg-p2p mailing list<br>
> <a href="mailto:mpiwg-p2p@lists.mpi-forum.org">mpiwg-p2p@lists.mpi-forum.org</a><br>
> <a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/<wbr>mailman/listinfo/mpiwg-p2p</a><br>
______________________________<wbr>_________________<br>
mpiwg-p2p mailing list<br>
<a href="mailto:mpiwg-p2p@lists.mpi-forum.org">mpiwg-p2p@lists.mpi-forum.org</a><br>
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/<wbr>mailman/listinfo/mpiwg-p2p</a></div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>mpiwg-p2p mailing list</span><br><span><a href="mailto:mpiwg-p2p@lists.mpi-forum.org">mpiwg-p2p@lists.mpi-forum.org</a></span><br><span><a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</a></span></div></blockquote></body></html>