<div dir="ltr">Dan,<div><br></div><div>At the last meeting, we came up with a proposal to allow info to be used for assertions. Should we work on pulling that together as a formal proposal, to read in June?</div><div><br></div><div> ~Jim.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 27, 2015 at 10:29 AM, Daniel Holmes <span dir="ltr"><<a href="mailto:dholmes@epcc.ed.ac.uk" target="_blank">dholmes@epcc.ed.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi All,<br>
<br>
I am cancelling the point-to-point teleconference today because I
have not had time to progress the work on communicator assertions
since last time and I am not aware of any other ongoing work for us
to talk about.<br>
<br>
Looking forward to figure out when the next meeting will take place,
I won't be available for the next two teleconferences due to
travelling. This means that the next meeting date would be 25th May,
i.e. one week before the face-to-face meeting in Chicago.<br>
<br>
I will send out a reminder nearer the time and will communicate any
progress in the interim via email.<br>
<br>
Cheers,<br>
Dan.<br>
<br>
<div>On 13/04/2015 10:32, Daniel Holmes
wrote:<br>
</div>
<blockquote type="cite">
Hi All,<br>
<br>
The next point-to-point teleconference will be today, Monday 13th
April 2015 at 11am Central US via webex.<br>
<br>
Connection details are on the point-to-point wiki page:<br>
<a href="https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/PtpWikiPage" target="_blank">https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/PtpWikiPage</a><br>
<br>
Agenda:<br>
0) Discuss/agree the to-do list (see below) that covers the next
two agenda items.<br>
1) "Can INFO keys change the semantic behaviour of MPI?" issue -
following the discussion at the face-to-face meeting, we seem to
have a workable way forward on this issue!<br>
2) New communicator INFO keys - it looks like these will be
allowed, so we should define a few and get a proposal ready for
the next face-to-face meeting<br>
3) Progress on Arecv and Fsend or ReceiveReduce?<br>
4) Other stuff?<br>
<br>
Cheers,<br>
Dan.<br>
<br>
<blockquote type="cite">Hi All,<br>
<br>
At the last telco meeting, Jim asked for a to-do list of the
tasks needed to move communicator assertions forward. Please
find below a first draft of such a task list. Could we agree
that this is a good list? If you see something odd/missing,
reply to this email group.<br>
<br>
<u>To-do list for communicator assertions</u><u><br>
</u><br>
0) Gather evidence to support "no-one will be affected by
backwards incompatibility".<br>
(e.g. chase Pavan, who volunteered to do this for major MPICH
users)<br>
1) Change behaviour of MPI_COMM_DUP so that INFO keys are *not*
propagated to new comm.<br>
(include AtoU: if you want to dup INFO use
MPI_COMM_DUP_WITH_INFO, with example)<br>
2) Discuss whether attributes (plus, anything else?) should be
propagated by MPI_COMM_DUP.<br>
(default presumption is yes, they should still be
propagated).<br>
3) Find all occurrence of language in the MPI Standard that
suggests INFO keys are hints.<br>
a) Change or remove any generic statements like "INFO keys
cannot change semantics".<br>
(e.g. change to "cannot change observable semantics" or
remove)<br>
b) For each occurrence, determine if it should continue to
suggest hint status<br>
(e.g. a particular key, most likely for the I/O keys but
maybe also some RMA keys)<br>
<br>
A) Convert ticket 381 into "make comm assertions doable"
proposal (by Jun 2015 - Chicago?)<br>
B) Get "no wildcard" INFO keys proposal ready for formal reading
(by Jun 2015 - Chicago?)<br>
C) Get "no ordering" INFO key proposal ready for formal reading
(by Jun 2015 - Chicago?)<br>
D) Get "no cancel" INFO keys proposal ready for formal reading
(by Jun 2015 - Chicago?)<br>
E) Discuss other INFO key proposals, e.g. "only wildcard", "no
non-blocking", "no underflow"<br>
<br>
Cheers,<br>
Dan.</blockquote>
<br>
<pre cols="72">--
Dan Holmes
Applications Consultant in HPC Research
EPCC, The University of Edinburgh
James Clerk Maxwell Building
The Kings Buildings
Peter Guthrie Tait Road
Edinburgh
EH9 3FD
T: <a href="tel:%2B44%280%29131%20651%203465" value="+441316513465" target="_blank">+44(0)131 651 3465</a>
E: <a href="mailto:dholmes@epcc.ed.ac.uk" target="_blank">dholmes@epcc.ed.ac.uk</a>
*Please consider the environment before printing this email.*</pre>
</blockquote>
<br>
<pre cols="72">--
Dan Holmes
Applications Consultant in HPC Research
EPCC, The University of Edinburgh
James Clerk Maxwell Building
The Kings Buildings
Peter Guthrie Tait Road
Edinburgh
EH9 3FD
T: <a href="tel:%2B44%280%29131%20651%203465" value="+441316513465" target="_blank">+44(0)131 651 3465</a>
E: <a href="mailto:dholmes@epcc.ed.ac.uk" target="_blank">dholmes@epcc.ed.ac.uk</a>
*Please consider the environment before printing this email.*</pre>
</div>
<br>The University of Edinburgh is a charitable body, registered in<br>
Scotland, with registration number SC005336.<br>
<br>_______________________________________________<br>
mpiwg-p2p mailing list<br>
<a href="mailto:mpiwg-p2p@lists.mpi-forum.org" target="_blank">mpiwg-p2p@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-p2p" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-p2p</a><br></blockquote></div><br></div></div>