- Mpi-21 - mailman3.cels.anl.gov

Re: [Mpi-21] Review of MPI-2.1 combined document
by unknown＠example.com 03 Mar '08

03 Mar '08

Some comments on chapter 7: Chapter 7: Page 247 line 34: MPI_VERSION should be 2 Page 250 lines 1-3: don't need to be red Page 253 lines 1-2: don't need to be red Page 253 line 14: Do we want to refer to MPI-2 specifically, or just as extended error handling ? Page 262: lines 1-11: Should MPI_ERR_KEYVAL be added to the list on page 261 ? Page 264: lines 6-16, should this be changed to reflect NULL arguments to MPI_Init() w/o backward reference to MPI 1.1 ? Rich On 3/3/08 3:39 PM, "Karl Feind" <kaf_at_[hidden]> wrote: > > Rolf & others, > > I have completed my review of Chapter 1 of the MPI 1 + 2 merging > document. > > It looks pretty good. > > I did notice two sentences on page 4, section 1.4, lines 13 and 14 > that apply to MPT 1.2 but not to MPI 2. This seems wrong in an MPI 2.1 > standard document. Can we delete the following two sentences from the > merged document? > > "Although no explicit support for threads is provided, the > interface has been designed so as not to prejudice their use. With > this version of MPI no support is provided for dynamic spawning > of tasks." > > If we do that, we could combine the sentence at line 11 about MIMD and > SPMD with the next paragraph that starts at line 15. This is the sentence > I'm referring to: > > "The interface is suitable for use by fully general MIMD > programs, as well as those written in the more restricted style > of SPMD." > > Karl Feind > > > On Sat, Feb 23, 2008 at 10:19:18PM +0100, Rolf Rabenseifner wrote: >> The first draft of the combined document MPI 1.x plus MPI 2.0 >> is ready for review !!! >> >> All necessary files can be found via >> http://www.hlrs.de/mpi/mpi21/ >> >> The files are stored in a restricted directory to prohibit that >> search engines can find the drafts. >> >> Dear reviewer: >> Please print your chapter with colors (!) and check all merging decisions. >> The colors will help to identify MPI 1.1-1.3 (black), >> MPI-2.0 (magenta) and new text that was necessary for the merge (red). >> >> The review should be finished a few days before the March meeting. >> Please post your review results on mpi-21_at_[hidden] as reply to this >> mail. >> >> Please note, which chapter you reviewed. >> >> Please refer with all comments exactly to page and line numbers of >> - MPI 1.1, the official Postscript version >> - MPI 2.0, the official Postscript version >> - MPI 2.1, draft 2008-02-23 from http://www.hlrs.de/mpi/mpi21/ >> - and the merging plan 2008-02-23, that you can find at same directory >> >> If you detect a problem, it is necessary that you try to propose >> a solution in similar notation as used in the merging plan. >> >> I have finished all except the merging of the MPI-1 C++ bindings >> into the chapters' text, and except of merging the Annexes. >> >> The Ballots 1-4 are also not included. >> In the moment, you need to review only the "merging". Nothing more. >> If you detect errors in the original standards, then please >> go through normal procedure, i.e., through the MPI 2.1 and MPI 2.2 >> ballots. >> >> And now, thank you very much that you have registered to do a >> review (if you are on the list below, done in Jan.2008 meeting). >> >> Good luck. >> >> Best regards >> Rolf >> >> ---------------------------------------------------- >> Frontmatter: (I've done a new proposal for the abstract, please check) >> - Rusty Lusk, Bill Gropp >> Chap. 1: Introduction to MPI >> - Rusty Lusk, Bill Gropp, Karl Feind, Adam Moody >> Chap. 2: MPI-2 Terms and Conventions >> - Tony Skjellum, Bill Gropp, Richard Barrett >> Chap. 3: Point-to-Point Communication (incl. sections from MPI-2 Misc. + 8.9) >> - Rich Graham, Jespar Larsson Traeff, George Bosilca, >> Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop >> Chap. 4: Collective Communication (incl. sections from MPI-2 Ext. Collect.) >> - Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, >> Bill Gropp, Adam Moody, Georg Bosilca >> Chap. 5: Groups, Context, and Communicators >> (incl. sections from MPI-2 Ext.Col. + 8.8) >> - Steven Ericsson-Zenith, Edgar Gabriel, >> Bill Gropp, Georg Bosilca, Robert Blackmore >> Chap. 6: Process Topologies >> - Rusty Lusk, Bill Gropp, Richard Barrett >> Chap. 7: MPI Environmental Management (incl. sections from MPI-2 Misc.) >> - Rich Graham, Jespar Larsson Traeff, George Bosilca, >> Steve Poole, Kannan Narasimhan, David Solt, B. Gropp >> Chap. 8: Miscellany >> - Rich Graham, George Bosilca, >> Steve Poole, Kannan Narasimhan, B. Gropp >> Chap. 9: Process Creation and Management >> - Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, >> Kalem Karian >> Chap. 10: One-Sided Communication >> - Ericsson-Zenith, Jespar Larsson Traeff, Martin Schulz, >> Bill Gropp, Darius Buntinas >> Chap. 11: External Interfaces >> - Bronis de Supinski, Bill Gropp >> Chap. 12: I/O >> - Rajeev Thakur, Joachim Worringen, Bill Gropp >> Chap. 13: Language Bindings >> - Jeff Squyres, Steve Poole, Purushotham Bangalore, >> Bill Gropp, Erez Haba, Alexander Supalov >> Chap. 14: Profiling Interface >> - Bronis de Supinski, Bill Gropp, Jeff Brown >> Bibliography: (is done automatically) >> - Rusty Lusk, Bill Gropp >> Annex A: (this chapter is not yet done - therefore no review for this) >> - Jeff Squyres, Steve Poole, Purushotham Bangalore, >> Bill Gropp, Alexander Supalov >> Index: (is done automatically) >> - Rusty Lusk, Bill Gropp >> >> >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >> _______________________________________________ >> Mpi-21 mailing list >> Mpi-21_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > _______________________________________________ > Mpi-21 mailing list > Mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21

1 0

Re: [Mpi-21] Review of MPI-2.1 combined document
by unknown＠example.com 03 Mar '08

03 Mar '08

Here is a first cut at comments on chapter 3. It looks good overall. Some of these comments, I am sure, are relevant once the automated part is done, as it involves text changes referring to the new document. Rich Chapter 3: ********** What about signed char - it should also be in the basic data section. In addition, this and wide char and unsigned long long should go into the data type table. Pate 34, line 1-6 - ok, but marked in red. They are from the original 1.1 document. Page 39 is incorrect. Lines 36-38. there is a standard definition in Fortran 2003 for fortran/C interoperability. Page 53: lines 30-34, need to get the correct reference based on the new document. (also, unmarked as moved text) What happened to section 4.5/4.5.1 from the MPI 2.0 standard. 4.5.2 made it over. Page 69 line 7 incorrectly states that there are four ways to create persistent communication request. The correct number is 5 - 4 send, 1 receive. Page 72, lines 34-38 need to reference the correct pages in the combined 2.1 document. Page 76 lines 1-4 should not be colored. They are from the 1.1 doc. Page 76 line 39: Do we still want to keep the name New in the title ? This also seems out of place. Page 77 lines 1-12 should be merged with the text, with the MPI 1.1 versions explicitly marked as deprecated. Page 94: lines 42-46, reference the correct pages in the new combined document. Page 95: lines 2-4, do we need this explanation ? Page 95: line 21-22, change to page reference in the new document. On 3/3/08 3:39 PM, "Karl Feind" <kaf_at_[hidden]> wrote: > > Rolf & others, > > I have completed my review of Chapter 1 of the MPI 1 + 2 merging > document. > > It looks pretty good. > > I did notice two sentences on page 4, section 1.4, lines 13 and 14 > that apply to MPT 1.2 but not to MPI 2. This seems wrong in an MPI 2.1 > standard document. Can we delete the following two sentences from the > merged document? > > "Although no explicit support for threads is provided, the > interface has been designed so as not to prejudice their use. With > this version of MPI no support is provided for dynamic spawning > of tasks." > > If we do that, we could combine the sentence at line 11 about MIMD and > SPMD with the next paragraph that starts at line 15. This is the sentence > I'm referring to: > > "The interface is suitable for use by fully general MIMD > programs, as well as those written in the more restricted style > of SPMD." > > Karl Feind > > > On Sat, Feb 23, 2008 at 10:19:18PM +0100, Rolf Rabenseifner wrote: >> The first draft of the combined document MPI 1.x plus MPI 2.0 >> is ready for review !!! >> >> All necessary files can be found via >> http://www.hlrs.de/mpi/mpi21/ >> >> The files are stored in a restricted directory to prohibit that >> search engines can find the drafts. >> >> Dear reviewer: >> Please print your chapter with colors (!) and check all merging decisions. >> The colors will help to identify MPI 1.1-1.3 (black), >> MPI-2.0 (magenta) and new text that was necessary for the merge (red). >> >> The review should be finished a few days before the March meeting. >> Please post your review results on mpi-21_at_[hidden] as reply to this >> mail. >> >> Please note, which chapter you reviewed. >> >> Please refer with all comments exactly to page and line numbers of >> - MPI 1.1, the official Postscript version >> - MPI 2.0, the official Postscript version >> - MPI 2.1, draft 2008-02-23 from http://www.hlrs.de/mpi/mpi21/ >> - and the merging plan 2008-02-23, that you can find at same directory >> >> If you detect a problem, it is necessary that you try to propose >> a solution in similar notation as used in the merging plan. >> >> I have finished all except the merging of the MPI-1 C++ bindings >> into the chapters' text, and except of merging the Annexes. >> >> The Ballots 1-4 are also not included. >> In the moment, you need to review only the "merging". Nothing more. >> If you detect errors in the original standards, then please >> go through normal procedure, i.e., through the MPI 2.1 and MPI 2.2 >> ballots. >> >> And now, thank you very much that you have registered to do a >> review (if you are on the list below, done in Jan.2008 meeting). >> >> Good luck. >> >> Best regards >> Rolf >> >> ---------------------------------------------------- >> Frontmatter: (I've done a new proposal for the abstract, please check) >> - Rusty Lusk, Bill Gropp >> Chap. 1: Introduction to MPI >> - Rusty Lusk, Bill Gropp, Karl Feind, Adam Moody >> Chap. 2: MPI-2 Terms and Conventions >> - Tony Skjellum, Bill Gropp, Richard Barrett >> Chap. 3: Point-to-Point Communication (incl. sections from MPI-2 Misc. + 8.9) >> - Rich Graham, Jespar Larsson Traeff, George Bosilca, >> Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop >> Chap. 4: Collective Communication (incl. sections from MPI-2 Ext. Collect.) >> - Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, >> Bill Gropp, Adam Moody, Georg Bosilca >> Chap. 5: Groups, Context, and Communicators >> (incl. sections from MPI-2 Ext.Col. + 8.8) >> - Steven Ericsson-Zenith, Edgar Gabriel, >> Bill Gropp, Georg Bosilca, Robert Blackmore >> Chap. 6: Process Topologies >> - Rusty Lusk, Bill Gropp, Richard Barrett >> Chap. 7: MPI Environmental Management (incl. sections from MPI-2 Misc.) >> - Rich Graham, Jespar Larsson Traeff, George Bosilca, >> Steve Poole, Kannan Narasimhan, David Solt, B. Gropp >> Chap. 8: Miscellany >> - Rich Graham, George Bosilca, >> Steve Poole, Kannan Narasimhan, B. Gropp >> Chap. 9: Process Creation and Management >> - Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, >> Kalem Karian >> Chap. 10: One-Sided Communication >> - Ericsson-Zenith, Jespar Larsson Traeff, Martin Schulz, >> Bill Gropp, Darius Buntinas >> Chap. 11: External Interfaces >> - Bronis de Supinski, Bill Gropp >> Chap. 12: I/O >> - Rajeev Thakur, Joachim Worringen, Bill Gropp >> Chap. 13: Language Bindings >> - Jeff Squyres, Steve Poole, Purushotham Bangalore, >> Bill Gropp, Erez Haba, Alexander Supalov >> Chap. 14: Profiling Interface >> - Bronis de Supinski, Bill Gropp, Jeff Brown >> Bibliography: (is done automatically) >> - Rusty Lusk, Bill Gropp >> Annex A: (this chapter is not yet done - therefore no review for this) >> - Jeff Squyres, Steve Poole, Purushotham Bangalore, >> Bill Gropp, Alexander Supalov >> Index: (is done automatically) >> - Rusty Lusk, Bill Gropp >> >> >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >> _______________________________________________ >> Mpi-21 mailing list >> Mpi-21_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > _______________________________________________ > Mpi-21 mailing list > Mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21

1 0

Ballot 3+4 - PDF for March meeting
by unknown＠example.com 03 Mar '08

03 Mar '08

Please can you print the MPI-2.1 Ballot 3 and 4 pdf-files for the March meeting. This may help that you can check open questions during the meeting together with your MPI 1.1 and MPI 2.0 standard (e.g. on your Laptop). Ballot 4 slides can be found here: (slides) http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/mpi_21… Ballot 3: (latex based document) http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/ballot… This files are also linked at http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/ At the March meeting, MPI-2.1 has 4 different topics: - Ballot 3 (clarifications to MPI 1 and 2) first official vote - Ballot 4 (clarifications to MPI 1 and 2) first official reading - MPI-1.3 (combinded document: MPI-1.1 + 1.2) review - MPI-2.1 (combinded document: MPI-1.3 + 2.0) review Best regards Rolf Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-21] Review of MPI-2.1 combined document
by unknown＠example.com 03 Mar '08

03 Mar '08

Rolf & others, I have completed my review of Chapter 1 of the MPI 1 + 2 merging document. It looks pretty good. I did notice two sentences on page 4, section 1.4, lines 13 and 14 that apply to MPT 1.2 but not to MPI 2. This seems wrong in an MPI 2.1 standard document. Can we delete the following two sentences from the merged document? "Although no explicit support for threads is provided, the interface has been designed so as not to prejudice their use. With this version of MPI no support is provided for dynamic spawning of tasks." If we do that, we could combine the sentence at line 11 about MIMD and SPMD with the next paragraph that starts at line 15. This is the sentence I'm referring to: "The interface is suitable for use by fully general MIMD programs, as well as those written in the more restricted style of SPMD." Karl Feind On Sat, Feb 23, 2008 at 10:19:18PM +0100, Rolf Rabenseifner wrote: > The first draft of the combined document MPI 1.x plus MPI 2.0 > is ready for review !!! > > All necessary files can be found via > http://www.hlrs.de/mpi/mpi21/ > > The files are stored in a restricted directory to prohibit that > search engines can find the drafts. > > Dear reviewer: > Please print your chapter with colors (!) and check all merging decisions. > The colors will help to identify MPI 1.1-1.3 (black), > MPI-2.0 (magenta) and new text that was necessary for the merge (red). > > The review should be finished a few days before the March meeting. > Please post your review results on mpi-21_at_[hidden] as reply to this > mail. > > Please note, which chapter you reviewed. > > Please refer with all comments exactly to page and line numbers of > - MPI 1.1, the official Postscript version > - MPI 2.0, the official Postscript version > - MPI 2.1, draft 2008-02-23 from http://www.hlrs.de/mpi/mpi21/ > - and the merging plan 2008-02-23, that you can find at same directory > > If you detect a problem, it is necessary that you try to propose > a solution in similar notation as used in the merging plan. > > I have finished all except the merging of the MPI-1 C++ bindings > into the chapters' text, and except of merging the Annexes. > > The Ballots 1-4 are also not included. > In the moment, you need to review only the "merging". Nothing more. > If you detect errors in the original standards, then please > go through normal procedure, i.e., through the MPI 2.1 and MPI 2.2 > ballots. > > And now, thank you very much that you have registered to do a > review (if you are on the list below, done in Jan.2008 meeting). > > Good luck. > > Best regards > Rolf > > ---------------------------------------------------- > Frontmatter: (I've done a new proposal for the abstract, please check) > - Rusty Lusk, Bill Gropp > Chap. 1: Introduction to MPI > - Rusty Lusk, Bill Gropp, Karl Feind, Adam Moody > Chap. 2: MPI-2 Terms and Conventions > - Tony Skjellum, Bill Gropp, Richard Barrett > Chap. 3: Point-to-Point Communication (incl. sections from MPI-2 Misc. + 8.9) > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop > Chap. 4: Collective Communication (incl. sections from MPI-2 Ext. Collect.) > - Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, > Bill Gropp, Adam Moody, Georg Bosilca > Chap. 5: Groups, Context, and Communicators > (incl. sections from MPI-2 Ext.Col. + 8.8) > - Steven Ericsson-Zenith, Edgar Gabriel, > Bill Gropp, Georg Bosilca, Robert Blackmore > Chap. 6: Process Topologies > - Rusty Lusk, Bill Gropp, Richard Barrett > Chap. 7: MPI Environmental Management (incl. sections from MPI-2 Misc.) > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp > Chap. 8: Miscellany > - Rich Graham, George Bosilca, > Steve Poole, Kannan Narasimhan, B. Gropp > Chap. 9: Process Creation and Management > - Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, > Kalem Karian > Chap. 10: One-Sided Communication > - Ericsson-Zenith, Jespar Larsson Traeff, Martin Schulz, > Bill Gropp, Darius Buntinas > Chap. 11: External Interfaces > - Bronis de Supinski, Bill Gropp > Chap. 12: I/O > - Rajeev Thakur, Joachim Worringen, Bill Gropp > Chap. 13: Language Bindings > - Jeff Squyres, Steve Poole, Purushotham Bangalore, > Bill Gropp, Erez Haba, Alexander Supalov > Chap. 14: Profiling Interface > - Bronis de Supinski, Bill Gropp, Jeff Brown > Bibliography: (is done automatically) > - Rusty Lusk, Bill Gropp > Annex A: (this chapter is not yet done - therefore no review for this) > - Jeff Squyres, Steve Poole, Purushotham Bangalore, > Bill Gropp, Alexander Supalov > Index: (is done automatically) > - Rusty Lusk, Bill Gropp > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > Mpi-21 mailing list > Mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21

1 0

Re: [Mpi-21] Ballot 4 - Re: MPI_Abort nit
by unknown＠example.com 03 Mar '08

03 Mar '08

I am OK with the proposed changes Dick Treumann - MPI Team/TCEM IBM Systems & Technology Group Dept 0lva / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote on 01/29/2008 04:06:49 AM: > This is a proposal for MPI 2.1, Ballot 4. > > I'm asking especially > Karl Feind, Bill Gropp, Andrew Lumsdaine, Dick Treumann, > the participants of the email-discussion in 2001, to review this proposal. > > This is a follow up to: > MPI_Abort > in http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi- > errata/index.html > with mail discussion in > http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi- > errata/discuss/abort/ > ___________________________________ > > Proposal: > MPI-1.1 Sect. 7.5, MPI_Abort, page 200, lines 23-26 read: > This routine makes a "best attempt" to abort all tasks in the > group of comm. This function does not require that the invoking > environment take any action with the error code. However, a Unix or > POSIX environment should handle this as a return errorcode from the > main program or an abort(errorcode). > but should read (" or an abort(errorcode)" removed): > This routine makes a "best attempt" to abort all tasks in the > group of comm. This function does not require that the invoking > environment take any action with the error code. However, a Unix or > POSIX environment should handle this as a return errorcode from the > main program. > ___________________________________ > Rationale for this clarification: > POSIX defines void abort(void). The routine void exit(int status) > may be used to implement "handle this as a return errorcode from the > main program". abort(errorcode) was not substituted by exit(errorcode) > because this is technically not enough, if the MPI implementation > wants to return it also from mpiexec, see next proposal. > ___________________________________ > > Proposal: > Add after MPI-1.1 Sect. 7.5, MPI_Abort, page 200, line 34 (end of rationale): > Advice to users. Whether the errorcode is returned from the executable > or from the MPI process startup mechanism (e.g., mpiexec), is an aspect > of quality of the MPI library but not mandatory. (End of advice tousers.) > ___________________________________ > Rationale for this clarification: > The intent of word "should" in "should handle this as a return > errorcode from the main program" is only a quality of implementation > aspect and not a must. This is not clear and can be misinterpreted. > ___________________________________ > > > Best regards > Rolf > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) *

1 0

Review of MPI-2.1 combined document
by unknown＠example.com 23 Feb '08

23 Feb '08

The first draft of the combined document MPI 1.x plus MPI 2.0 is ready for review !!! All necessary files can be found via http://www.hlrs.de/mpi/mpi21/ The files are stored in a restricted directory to prohibit that search engines can find the drafts. Dear reviewer: Please print your chapter with colors (!) and check all merging decisions. The colors will help to identify MPI 1.1-1.3 (black), MPI-2.0 (magenta) and new text that was necessary for the merge (red). The review should be finished a few days before the March meeting. Please post your review results on mpi-21_at_[hidden] as reply to this mail. Please note, which chapter you reviewed. Please refer with all comments exactly to page and line numbers of - MPI 1.1, the official Postscript version - MPI 2.0, the official Postscript version - MPI 2.1, draft 2008-02-23 from http://www.hlrs.de/mpi/mpi21/ - and the merging plan 2008-02-23, that you can find at same directory If you detect a problem, it is necessary that you try to propose a solution in similar notation as used in the merging plan. I have finished all except the merging of the MPI-1 C++ bindings into the chapters' text, and except of merging the Annexes. The Ballots 1-4 are also not included. In the moment, you need to review only the "merging". Nothing more. If you detect errors in the original standards, then please go through normal procedure, i.e., through the MPI 2.1 and MPI 2.2 ballots. And now, thank you very much that you have registered to do a review (if you are on the list below, done in Jan.2008 meeting). Good luck. Best regards Rolf ---------------------------------------------------- Frontmatter: (I've done a new proposal for the abstract, please check) - Rusty Lusk, Bill Gropp Chap. 1: Introduction to MPI - Rusty Lusk, Bill Gropp, Karl Feind, Adam Moody Chap. 2: MPI-2 Terms and Conventions - Tony Skjellum, Bill Gropp, Richard Barrett Chap. 3: Point-to-Point Communication (incl. sections from MPI-2 Misc. + 8.9) - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop Chap. 4: Collective Communication (incl. sections from MPI-2 Ext. Collect.) - Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, Bill Gropp, Adam Moody, Georg Bosilca Chap. 5: Groups, Context, and Communicators (incl. sections from MPI-2 Ext.Col. + 8.8) - Steven Ericsson-Zenith, Edgar Gabriel, Bill Gropp, Georg Bosilca, Robert Blackmore Chap. 6: Process Topologies - Rusty Lusk, Bill Gropp, Richard Barrett Chap. 7: MPI Environmental Management (incl. sections from MPI-2 Misc.) - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp Chap. 8: Miscellany - Rich Graham, George Bosilca, Steve Poole, Kannan Narasimhan, B. Gropp Chap. 9: Process Creation and Management - Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, Kalem Karian Chap. 10: One-Sided Communication - Ericsson-Zenith, Jespar Larsson Traeff, Martin Schulz, Bill Gropp, Darius Buntinas Chap. 11: External Interfaces - Bronis de Supinski, Bill Gropp Chap. 12: I/O - Rajeev Thakur, Joachim Worringen, Bill Gropp Chap. 13: Language Bindings - Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Erez Haba, Alexander Supalov Chap. 14: Profiling Interface - Bronis de Supinski, Bill Gropp, Jeff Brown Bibliography: (is done automatically) - Rusty Lusk, Bill Gropp Annex A: (this chapter is not yet done - therefore no review for this) - Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Alexander Supalov Index: (is done automatically) - Rusty Lusk, Bill Gropp Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

MPI 1.3 - errata from Ballot 3 and 4
by unknown＠example.com 10 Feb '08

10 Feb '08

Proposal: The following topics on http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/index.… hould be marked with "To be included also in MPI 1.3" ----------------------------------------------------- Error in MPI_Scan Example Error in MPI-1, Example 3.12 Error in MPI-1, Example 3.12, continued Error in MPI-1, Example 3.13 Error in MPI-1, Examples 3.17 and 3.18 Error in MPI-1, Example 3.34 Use of strlen in MPI-1, chapter 3 Formatting error in discussion of persistent communication in MPI-1 Datatypes and MPI_PROBE MPI_Abort Error handler for multiple completions (if ready for March meeting) Not marked and therefore not included in MPI1.3 should be: ---------------------------------------------------------- Questions about Graph_create, Cart_create, and Cart_coords (not included, because it may require Impl.Effort, i.e. new version number 2.1) Error handler for multiple completions (if ready for March meeting) (not included or included, --- must be decided when proposal available) MPI_FINALIZE in MPI-2 (with spawn) (if ready for March meeting) (not included, because MPI&Threads is MPI 2) MPI_GET_PROCESSOR_NAME and Fortran (not included, because it may require Impl.Effort, i.e. new version number 2.1) Change "INOUT" to "IN" for MPI Handle Parameters in several routines (not included, because related to new MPI-2 Chapter 2 Terms&... Text) I hope I captured all currently proposed MPI-1.1 clarifications in Ballot 3 and 4. Best regards Rolf Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [mpi-21] Ballot 4 - all proposal now on the web
by unknown＠example.com 07 Feb '08

07 Feb '08

Not best wording. I used - Selected for MPI 2.1 Ballot x if I would like to have it done in Ballot x but there is no proposal -- may be because there is no need, i.e., this topic is finished -- may be we are waiting for somebody who is writing the final proposal - Proposed for MPI 2.1 Ballot x means, somebody has written a proposal that ready for voting. At least in one case, the wrong word isused on the errata page. On March meeting, we can vote only on proposals that are really existing. I hope, somebody (not limited to discussion members) will write some of the pending proposals. Best regards Rolf PS: Selected for MPI 2.2 meant that the topic was on Bill's slide at Jan. 2008 meeting. On Thu, 07 Feb 2008 13:30:21 -0500 Terry Dontje <Terry.Dontje_at_[hidden]> wrote: >Can you clarify the difference between a topic marked "Selected for MPI >2.X Ballot Y" and "Proposed for MPI 2.X Ballot Y"? > >--td Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [mpi-21] Ballot 4 - all proposal now on the web
by unknown＠example.com 07 Feb '08

07 Feb '08

Can you clarify the difference between a topic marked "Selected for MPI 2.X Ballot Y" and "Proposed for MPI 2.X Ballot Y"? --td "selected for Rolf Rabenseifner wrote: > Hi all interested in MPI 2.1! > > all proposals are now on the Web: > http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/index.… > > Please, check whether I've done something wrong. > > Although I've written the details of some of these proposals, > I try to be the moderator of the discussion. > In some cases, when I saw that several options are possible, > and none of these seemed to me technically obvious or perfect, > I've put all these options on the web page to allow that the > MPI Forum can make those decisions at the March meeting. > > Please check, whether I've done something wrong or whether > I have to add an additional alternative proposal > (in this case, please write the proposal with all necessary > details (as text) that I can make a cut&paste to the web page > plus additional HTML formatting). > > Please check for the RED flag Ballot 4 topics > and help that the missing proposals are written. > > Best regards > Rolf > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21 >

1 0

Re: [mpi-21] Ballot 4 proposal: fix attribute example 4.13
by unknown＠example.com 07 Feb '08

07 Feb '08

On Feb 7, 2008, at 12:51 PM, Rolf Rabenseifner wrote: >>> Additional proposal (B): Add at the end of the previous text: >>> The application must not change this integer valued attribute >>> at the returned address. >> >> I had to think about this quite a bit before I "got it" -- you're >> saying that when an integer-valued attribute is set (from fortran), >> the MPI implementation must be caching the value internally and then >> returning a pointer to that internally cached value. Hence, the >> address is only valid as long as the MPI object is valid. >> >> However, I'm not sure about the requirement of not changing the value >> (for integer-valued attributes). If you MPI_xxx_get_attr from C and >> change the value, it'll be changed for any subsequent >> MPI_xxx_get_attr >> calls from C or Fortran. However, if you MPI_xxx_get_attr from >> Fortran and change the value, the next call to MPI_xxx_get_attr will >> have the original value. >> >> Are you just trying to avoid this disparity? > > Normally, MPI never gives the application the right to change > anything in a opaque object without calling an MPI routine. > > C-routine MPI_xxx_get_attr is called with a handle to a opaque object > that has stored a Fortran integer-valued attribute. > IF we allow, that MPI_xxx_get_attr returns a pointer to foo > and foo contains the value of such fortran-integer-attribute, > AND IF we allow that a subsequent same call to MPI_xxx_get_attr > returns > the same pointer to same foo, > AND IF we allow that the application may change the value of foo, > THEN I would report: > foo is part of the opaque object > and we allowed that the application has changed the value without > calling MPI_xxx_set_attr. Ah, I can see this rationale. Good point. It might be helpful to have some synopsis of your above text should be part of a "Rationale" block in the official text, because that's not immediately obvious. What I have difficulty resolving, though, is that this would be an asymmetrical exception: 1. set attribute in fortran, get attribute in fortran: allowed to change 2. set attribute in fortran, get attribute in C: *NOT* allowed to change 3. set attribute in C, get attribute in C: allowed to change 4. set attribute in C, get attribute in fortran: allowed to change I can see your rationale; it's just that this asymmetry makes me... uncomfortable. Indeed, case 2 is the only case where the life of the MPI object is related to the life of the attribute. That's just weird to me. But I could probably be convinced that this is ok -- after all, who really cares about attributes! ;-) (e.g., the set-in-C-get-in- fortran case is almost useless...) > If we do not want this, then there are two solutions: > - restrictive: to forbid changing the value from C directly; > - memory wasting: producing always a new foo in each call to > MPI_xxx_get_attr. The memory wasting solution is no good -- we'd either have to say that the caller is reponsible for free()'ing the returned pointer or accept a memory leak, because there's no way for the caller to give the pointer back to MPI and say "I'm done with this". -- Jeff Squyres Cisco Systems

1 0