- mpiwg-p2p - mailman3.cels.anl.gov

Re: [mpiwg-p2p] Next meeting: 24th October 2016 11am Central US
by Jim Dinan 24 Oct '16

24 Oct '16

I can also create a Lync meeting for today, if we need one. On Mon, Oct 24, 2016 at 12:10 PM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > Hi Jim, > > I think that Jeff S is creating a new WebEx for us - I’m going to give him > a few more minutes. > > Cheers, > Dan. > > On 24 Oct 2016, at 17:07, Jim Dinan <james.dinan(a)gmail.com> wrote: > > I'm having trouble getting the webex to work, but I was able to dial in > directly using the number below. > > ~Jim. > > Audio connection: > > +1-866-432-9903 Call-in toll-free number (US/Canada) > +1-408-525-6800 Call-in toll number (US/Canada) > > Access code: 201 343 896 > > On Fri, Oct 21, 2016 at 9:22 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > >> Hi all, >> >> The next point-to-point teleconference will be on Monday 24th October >> 2016 at 11am Central US via webex. >> >> Connection details are on the p2p wiki: >> https://github.com/mpiwg-p2p/p2p-issues/wiki >> >> Agenda: >> >> 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 completed these changes and Rolf has checked them. >> We will need 4 reviewers (Rolf + 3). >> >> 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. >> >> 3) Fixing INFO_GET/SET (issue #63): I have created a new issue for this >> and there has been some discussion in the comments and via email. This >> looks like it needs major re-design work. >> >> Slides from Sept 2016 meeting with notes on discussion and way forward: >> https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3p >> XJjqQs1tlnlO-6TJXIC8G8Q/edit?usp=sharing >> >> In addition to this meeting (24th Oct), we will only have 7th Nov before >> 21st Nov, which is the 2-week deadline for the next face-to-face meeting. >> >> Plan: >> Withdraw #11 from vote on 23rd Sept. [DONE] >> Create #new and produce a first draft of the text for the Standard. [DONE] >> Discuss at the meeting on 10th Oct. [INQUORATE] >> Adjust text for the Standard and produce a first draft of the slides for >> presenting at the next face-to-face. >> Discuss at the meeting on 24th Oct. >> Find and fix all the references and stuff that's needed for a proper >> proposal (Rolf-proofing). >> Discuss at the meeting on 7th Nov. >> Final adjustments for #63, text, and slides. >> Announce #11 (1st vote) and #63 (reading) to mpi-forum list by 21st Nov. >> >> If we discover during the work on #63 that #11 needs to be adjusted then >> we can re-start its formal procedure with a reading in December. >> >> Cheers, >> Dan. >> >> -- >> 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: dholmes(a)epcc.ed.ac.uk >> >> *Please consider the environment before printing this email.* >> >> >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >> _______________________________________________ >> mpiwg-p2p mailing list >> mpiwg-p2p(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p >> > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > > > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Next meeting: 24th October 2016 11am Central US
by Dan Holmes 24 Oct '16

24 Oct '16

Hi Jim, I think that Jeff S is creating a new WebEx for us - I’m going to give him a few more minutes. Cheers, Dan. > On 24 Oct 2016, at 17:07, Jim Dinan <james.dinan(a)gmail.com> wrote: > > I'm having trouble getting the webex to work, but I was able to dial in directly using the number below. > > ~Jim. > > Audio connection: > > +1-866-432-9903 Call-in toll-free number (US/Canada) > +1-408-525-6800 Call-in toll number (US/Canada) > > Access code: 201 343 896 > > On Fri, Oct 21, 2016 at 9:22 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk <mailto:[email protected]>> wrote: > Hi all, > > The next point-to-point teleconference will be on Monday 24th October 2016 at 11am Central US via webex. > > Connection details are on the p2p wiki: > https://github.com/mpiwg-p2p/p2p-issues/wiki <https://github.com/mpiwg-p2p/p2p-issues/wiki> > > Agenda: > > 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 completed these changes and Rolf has checked them. We will need 4 reviewers (Rolf + 3). > > 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. > > 3) Fixing INFO_GET/SET (issue #63): I have created a new issue for this and there has been some discussion in the comments and via email. This looks like it needs major re-design work. > > Slides from Sept 2016 meeting with notes on discussion and way forward: > https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T… <https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T…> > > In addition to this meeting (24th Oct), we will only have 7th Nov before 21st Nov, which is the 2-week deadline for the next face-to-face meeting. > > Plan: > Withdraw #11 from vote on 23rd Sept. [DONE] > Create #new and produce a first draft of the text for the Standard. [DONE] > Discuss at the meeting on 10th Oct. [INQUORATE] > Adjust text for the Standard and produce a first draft of the slides for presenting at the next face-to-face. > Discuss at the meeting on 24th Oct. > Find and fix all the references and stuff that's needed for a proper proposal (Rolf-proofing). > Discuss at the meeting on 7th Nov. > Final adjustments for #63, text, and slides. > Announce #11 (1st vote) and #63 (reading) to mpi-forum list by 21st Nov. > > If we discover during the work on #63 that #11 needs to be adjusted then we can re-start its formal procedure with a reading in December. > > Cheers, > Dan. > > -- > 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 <tel:%2B44%280%29131%20651%203465> > E: dholmes(a)epcc.ed.ac.uk <mailto:[email protected]> > > *Please consider the environment before printing this email.* > > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org <mailto:[email protected]> > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p> > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Next meeting: 24th October 2016 11am Central US
by Jim Dinan 24 Oct '16

24 Oct '16

I'm having trouble getting the webex to work, but I was able to dial in directly using the number below. ~Jim. Audio connection: +1-866-432-9903 Call-in toll-free number (US/Canada) +1-408-525-6800 Call-in toll number (US/Canada) Access code: 201 343 896 On Fri, Oct 21, 2016 at 9:22 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > Hi all, > > The next point-to-point teleconference will be on Monday 24th October 2016 > at 11am Central US via webex. > > Connection details are on the p2p wiki: > https://github.com/mpiwg-p2p/p2p-issues/wiki > > Agenda: > > 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 completed these changes and Rolf has checked them. > We will need 4 reviewers (Rolf + 3). > > 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. > > 3) Fixing INFO_GET/SET (issue #63): I have created a new issue for this > and there has been some discussion in the comments and via email. This > looks like it needs major re-design work. > > Slides from Sept 2016 meeting with notes on discussion and way forward: > https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tl > nlO-6TJXIC8G8Q/edit?usp=sharing > > In addition to this meeting (24th Oct), we will only have 7th Nov before > 21st Nov, which is the 2-week deadline for the next face-to-face meeting. > > Plan: > Withdraw #11 from vote on 23rd Sept. [DONE] > Create #new and produce a first draft of the text for the Standard. [DONE] > Discuss at the meeting on 10th Oct. [INQUORATE] > Adjust text for the Standard and produce a first draft of the slides for > presenting at the next face-to-face. > Discuss at the meeting on 24th Oct. > Find and fix all the references and stuff that's needed for a proper > proposal (Rolf-proofing). > Discuss at the meeting on 7th Nov. > Final adjustments for #63, text, and slides. > Announce #11 (1st vote) and #63 (reading) to mpi-forum list by 21st Nov. > > If we discover during the work on #63 that #11 needs to be adjusted then > we can re-start its formal procedure with a reading in December. > > Cheers, > Dan. > > -- > 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: dholmes(a)epcc.ed.ac.uk > > *Please consider the environment before printing this email.* > > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Next meeting: 24th October 2016 11am Central US
by Dan Holmes 21 Oct '16

21 Oct '16

Hi all, The next point-to-point teleconference will be on Monday 24th October 2016 at 11am Central US via webex. Connection details are on the p2p wiki: https://github.com/mpiwg-p2p/p2p-issues/wiki <https://github.com/mpiwg-p2p/p2p-issues/wiki> Agenda: 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 completed these changes and Rolf has checked them. We will need 4 reviewers (Rolf + 3). 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. 3) Fixing INFO_GET/SET (issue #63): I have created a new issue for this and there has been some discussion in the comments and via email. This looks like it needs major re-design work. Slides from Sept 2016 meeting with notes on discussion and way forward: https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T… <https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T…> In addition to this meeting (24th Oct), we will only have 7th Nov before 21st Nov, which is the 2-week deadline for the next face-to-face meeting. Plan: Withdraw #11 from vote on 23rd Sept. [DONE] Create #new and produce a first draft of the text for the Standard. [DONE] Discuss at the meeting on 10th Oct. [INQUORATE] Adjust text for the Standard and produce a first draft of the slides for presenting at the next face-to-face. Discuss at the meeting on 24th Oct. Find and fix all the references and stuff that's needed for a proper proposal (Rolf-proofing). Discuss at the meeting on 7th Nov. Final adjustments for #63, text, and slides. Announce #11 (1st vote) and #63 (reading) to mpi-forum list by 21st Nov. If we discover during the work on #63 that #11 needs to be adjusted then we can re-start its formal procedure with a reading in December. Cheers, Dan. -- 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: dholmes(a)epcc.ed.ac.uk *Please consider the environment before printing this email.* The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Next meeting: 10th October 2016 11am Central US
by Jim Dinan 19 Oct '16

19 Oct '16

We could state that the output from get_info is implementation defined. With the caveat that a user must be able to pass the output from get_info to a subsequent communicator creation call and get back a communicator with the same behavior as the original one. On Mon, Oct 17, 2016 at 12:06 PM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > Hi Jim, > > 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. > > 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. > > Cheers, > Dan. > > On 17 Oct 2016, at 16:49, Jim Dinan <james.dinan(a)gmail.com> wrote: > > Ahh crud, sorry I missed this meeting. I've got the next one on my > calendar and should be there. > > 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? > > ~Jim. > > On Fri, Oct 7, 2016 at 4:24 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > >> Hi all, >> >> The next point-to-point teleconference will be on Monday 10th October >> 2016 at 11am Central US via webex. >> >> Connection details are on the p2p wiki: >> https://github.com/mpiwg-p2p/p2p-issues/wiki >> >> Agenda: >> >> 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). >> >> 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. >> >> 3) Fixing INFO_GET/SET (issue #new): Jim and I have discussed a plan to >> get this moving. >> >> Slides from Sept 2016 meeting with notes on discussion and way forward: >> https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3p >> XJjqQs1tlnlO-6TJXIC8G8Q/edit?usp=sharing >> >> 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. >> >> Plan: >> Withdraw #11 from vote on 23rd Sept. [DONE] >> Create #new and produce a first draft of the text for the Standard. [IN >> PROGRESS] >> Discuss at the meeting on 10th Oct. >> Adjust text for the Standard and produce a first draft of the slides for >> presenting at the next face-to-face. >> Discuss at the meeting on 24th Oct. >> Find and fix all the references and stuff that's needed for a proper >> proposal (Rolf-proofing). >> Discuss at the meeting on 7th Nov. >> Final adjustments for #new, text, and slides. >> Announce #11 (1st vote) and #new (reading) to mpi-forum list by 21st Nov. >> >> 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. >> >> >> >> Cheers, >> Dan. >> >> -- >> 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: dholmes(a)epcc.ed.ac.uk >> >> *Please consider the environment before printing this email.* >> >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >> _______________________________________________ >> mpiwg-p2p mailing list >> mpiwg-p2p(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p >> > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > > > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Next meeting: 10th October 2016 11am Central US
by Dan Holmes 17 Oct '16

17 Oct '16

Hi Jim, 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. 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. Cheers, Dan. > On 17 Oct 2016, at 16:49, Jim Dinan <james.dinan(a)gmail.com> wrote: > > Ahh crud, sorry I missed this meeting. I've got the next one on my calendar and should be there. > > 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? > > ~Jim. > > On Fri, Oct 7, 2016 at 4:24 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk <mailto:[email protected]>> wrote: > Hi all, > > The next point-to-point teleconference will be on Monday 10th October 2016 at 11am Central US via webex. > > Connection details are on the p2p wiki: > https://github.com/mpiwg-p2p/p2p-issues/wiki <https://github.com/mpiwg-p2p/p2p-issues/wiki> > > Agenda: > > 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). > > 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. > > 3) Fixing INFO_GET/SET (issue #new): Jim and I have discussed a plan to get this moving. > > Slides from Sept 2016 meeting with notes on discussion and way forward: > https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T… <https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T…> > > 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. > > Plan: > Withdraw #11 from vote on 23rd Sept. [DONE] > Create #new and produce a first draft of the text for the Standard. [IN PROGRESS] > Discuss at the meeting on 10th Oct. > Adjust text for the Standard and produce a first draft of the slides for presenting at the next face-to-face. > Discuss at the meeting on 24th Oct. > Find and fix all the references and stuff that's needed for a proper proposal (Rolf-proofing). > Discuss at the meeting on 7th Nov. > Final adjustments for #new, text, and slides. > Announce #11 (1st vote) and #new (reading) to mpi-forum list by 21st Nov. > > 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. > > > > Cheers, > Dan. > > -- > 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 <tel:%2B44%280%29131%20651%203465> > E: dholmes(a)epcc.ed.ac.uk <mailto:[email protected]> > > *Please consider the environment before printing this email.* > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org <mailto:[email protected]> > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p> > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org <mailto:[email protected]> > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p> The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Next meeting: 10th October 2016 11am Central US
by Jim Dinan 17 Oct '16

17 Oct '16

Ahh crud, sorry I missed this meeting. I've got the next one on my calendar and should be there. 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? ~Jim. On Fri, Oct 7, 2016 at 4:24 AM, Dan Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > Hi all, > > The next point-to-point teleconference will be on Monday 10th October 2016 > at 11am Central US via webex. > > Connection details are on the p2p wiki: > https://github.com/mpiwg-p2p/p2p-issues/wiki > > Agenda: > > 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). > > 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. > > 3) Fixing INFO_GET/SET (issue #new): Jim and I have discussed a plan to > get this moving. > > Slides from Sept 2016 meeting with notes on discussion and way forward: > https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tl > nlO-6TJXIC8G8Q/edit?usp=sharing > > 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. > > Plan: > Withdraw #11 from vote on 23rd Sept. [DONE] > Create #new and produce a first draft of the text for the Standard. [IN > PROGRESS] > Discuss at the meeting on 10th Oct. > Adjust text for the Standard and produce a first draft of the slides for > presenting at the next face-to-face. > Discuss at the meeting on 24th Oct. > Find and fix all the references and stuff that's needed for a proper > proposal (Rolf-proofing). > Discuss at the meeting on 7th Nov. > Final adjustments for #new, text, and slides. > Announce #11 (1st vote) and #new (reading) to mpi-forum list by 21st Nov. > > 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. > > > > Cheers, > Dan. > > -- > 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: dholmes(a)epcc.ed.ac.uk > > *Please consider the environment before printing this email.* > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p > _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Next meeting: 10th October 2016 11am Central US
by Dan Holmes 07 Oct '16

07 Oct '16

Hi all, The next point-to-point teleconference will be on Monday 10th October 2016 at 11am Central US via webex. Connection details are on the p2p wiki: https://github.com/mpiwg-p2p/p2p-issues/wiki <https://github.com/mpiwg-p2p/p2p-issues/wiki> Agenda: 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). 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. 3) Fixing INFO_GET/SET (issue #new): Jim and I have discussed a plan to get this moving. Slides from Sept 2016 meeting with notes on discussion and way forward: https://docs.google.com/presentation/d/10EPCx2LuJ0BWCeUXIG3pXJjqQs1tlnlO-6T… 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. Plan: Withdraw #11 from vote on 23rd Sept. [DONE] Create #new and produce a first draft of the text for the Standard. [IN PROGRESS] Discuss at the meeting on 10th Oct. Adjust text for the Standard and produce a first draft of the slides for presenting at the next face-to-face. Discuss at the meeting on 24th Oct. Find and fix all the references and stuff that's needed for a proper proposal (Rolf-proofing). Discuss at the meeting on 7th Nov. Final adjustments for #new, text, and slides. Announce #11 (1st vote) and #new (reading) to mpi-forum list by 21st Nov. 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. Cheers, Dan. -- 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: dholmes(a)epcc.ed.ac.uk <mailto:[email protected]> *Please consider the environment before printing this email.* The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Re: [mpiwg-p2p] Mailing List Migration Happening Today
by Bland, Wesley 03 Oct '16

03 Oct '16

The list should be available again. It's possible that things might not work in your particular area yet if your DNS updates slowly. > On Oct 3, 2016, at 9:46 AM, Bland, Wesley <wesley.bland(a)intel.com> wrote: > > After delaying the migration a bit to avoid interrupting the forum meeting and EuroMPI, we're ready to do the migration today. It's possible that there will be some brief outages between now and the end of the day while DNS records are updated and most likely any emails sent today could end up not getting archived correctly. > > Make sure you are using the correct address for this list in the future as any aliases that might have worked in the past will almost certainly not work in the future: > > mpiwg-p2p(a)lists.mpi-forum.org > > Thanks, > Wesley > _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-p2p

1 0

Mailing List Migration Happening Today
by Bland, Wesley 03 Oct '16

03 Oct '16

After delaying the migration a bit to avoid interrupting the forum meeting and EuroMPI, we're ready to do the migration today. It's possible that there will be some brief outages between now and the end of the day while DNS records are updated and most likely any emails sent today could end up not getting archived correctly. Make sure you are using the correct address for this list in the future as any aliases that might have worked in the past will almost certainly not work in the future: mpiwg-p2p(a)lists.mpi-forum.org Thanks, Wesley _______________________________________________ mpiwg-p2p mailing list mpiwg-p2p(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-p2p

1 0