<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Jim,<div class=""><br class=""></div><div class="">Another thought that occurred to me was getting rid of get_info - in favour of using the MPI_T interface to figure out what the MPI library has actually done. There is a well-defined semantic for MPI_T variables w.r.t. when can the value change, what variables exist, what do particular values of particular variables mean, etc.</div><div class=""><br class=""></div><div class="">We could propose to standardise some MPI_T variables, such as MPI_ANY_TAG_is_supported or MPI_ANY_TAG_is_permitted, to replace the get_info feedback mechanism.</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 17 Oct 2016, at 16:49, Jim Dinan <<a href="mailto:james.dinan@gmail.com" class="">james.dinan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Ahh crud, sorry I missed this meeting. I've got the next one on my calendar and should be there.<div class=""><br class=""></div><div class="">I was recently telling a colleague about this get_info stuff and he made a suggestion that initially sounded nuts, but is becoming more appealing. Can we just remove set_info? Many of the challenges we have are caused by this function, and yet its value is questionable. What do you think? Worth looking into?</div><div class=""><br class=""></div><div class=""> ~Jim.</div></div><div class="gmail_extra" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""><div class="gmail_quote">On Fri, Oct 7, 2016 at 4:24 AM, Dan Holmes<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:dholmes@epcc.ed.ac.uk" target="_blank" class="">dholmes@epcc.ed.ac.uk</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class="">Hi all,<div class=""><br class=""></div><div class="">The next point-to-point teleconference will be on Monday 10th October 2016 at 11am Central US via webex.</div><br class="">Connection details are on the p2p wiki:<br class=""><a href="https://github.com/mpiwg-p2p/p2p-issues/wiki" target="_blank" class="">https://github.com/mpiwg-p2p/<wbr class="">p2p-issues/wiki</a><br class=""><br class="">Agenda:<div class=""><br class=""></div><div class="">1) Deprecation of send cancel (issue #26): at the Sept 2016 meeting, Rolf correctly pointed out multiple additional administrative changes that are needed for this. I have a list of these changes and I am working through them. Once that is done, we will need 4 reviewers (Rolf + 3).</div><div class=""><br class=""></div><div class="">2) Communicator assertions (issue #11): at the Sept 2016 meeting, Pavan et al raised the valid objection that fixing the train-wreck of INFO_GET/SET may have knock-on effects on this and so we should delay the vote on it until we have the full picture.</div><div class=""><br class=""></div><div class="">3) Fixing INFO_GET/SET (issue #new): Jim and I have discussed a plan to get this moving.</div><div class=""><br class=""></div><div class="">Slides from Sept 2016 meeting with notes on discussion and way forward:</div><div class=""><a href="https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6TJXIC8G8Q/edit?usp=sharing" target="_blank" class="">https://docs.google.com/<wbr class="">presentation/d/<wbr class="">10EPCx2LuJ0BWCeUXIG3pXJjqQs1tl<wbr class="">nlO-6TJXIC8G8Q/edit?usp=<wbr class="">sharing</a></div><div class=""><br class=""></div><div class="">In addition to our next meeting (10th Oct), we will have 24th Oct and 7th Nov before 21st Nov, which is the 2-week deadline for the next face-to-face meeting.</div><div class=""><br class=""></div><div class="">Plan:</div><div class=""><div class="">Withdraw #11 from vote on 23rd Sept. [DONE]</div><div class="">Create #new and produce a first draft of the text for the Standard. [IN PROGRESS]</div><div class="">Discuss at the meeting on 10th Oct.</div><div class="">Adjust text for the Standard and produce a first draft of the slides for presenting at the next face-to-face.</div><div class="">Discuss at the meeting on 24th Oct.</div><div class="">Find and fix all the references and stuff that's needed for a proper proposal (Rolf-proofing).</div><div class="">Discuss at the meeting on 7th Nov.</div><div class="">Final adjustments for #new, text, and slides.</div><div class="">Announce #11 (1st vote) and #new (reading) to mpi-forum list by 21st Nov.</div><div class=""><br class=""></div><div class="">If we discover during the work on #new that #11 needs to be adjusted then we can re-start its formal procedure with a reading in December.</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,<br class="">Dan.<br class=""><br class="">-- <br class="">Dan Holmes<br class="">Applications Consultant in HPC Research<br class="">EPCC, The University of Edinburgh<br class="">James Clerk Maxwell Building<br class="">The Kings Buildings<br class="">Peter Guthrie Tait Road<br class="">Edinburgh<br class="">EH9 3FD<br class="">T:<span class="Apple-converted-space"> </span><a href="tel:%2B44%280%29131%20651%203465" value="+441316513465" target="_blank" class="">+44(0)131 651 3465</a><br class="">E: <a href="mailto:dholmes@epcc.ed.ac.uk" target="_blank" class="">dholmes@epcc.ed.ac.uk</a><br class=""><br class="">*Please consider the environment before printing this email.*</div></div><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=""></blockquote></div><br class=""></div><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">mpiwg-p2p mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="mailto:mpiwg-p2p@lists.mpi-forum.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">mpiwg-p2p@lists.mpi-forum.org</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p</a></div></blockquote></div><br class=""></div></body></html>