<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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.<br>
<br>
<div class="moz-cite-prefix">On 13/03/2015 19:22, Daniel Holmes
wrote:<br>
</div>
<blockquote cite="mid:550338DB.2000009@epcc.ed.ac.uk" type="cite">Hi
All, <br>
<br>
The next point-to-point teleconference will be on Monday 16th
March 2015 at 11am Central US via webex. <br>
<br>
Connection details are on the point-to-point wiki page: <br>
<a class="moz-txt-link-freetext"
href="https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/PtpWikiPage">https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/PtpWikiPage</a>
<br>
<br>
Agenda: <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>
<br>
<br>
<pre class="moz-signature" 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: +44(0)131 651 3465
E: <a class="moz-txt-link-abbreviated" href="mailto:dholmes@epcc.ed.ac.uk">dholmes@epcc.ed.ac.uk</a>
*Please consider the environment before printing this email.*</pre>
</body>
</html>