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

Re: [Mpi-21] Formal MPI-2.1 Review
by unknown＠example.com 28 Apr '08

28 Apr '08

Hello Rolf, please find enclosed the changes to MPI-2.1 Chapter12 (compared to the version April 19 2008). Thanks, Rainer On Monday 21 April 2008 20:38, Rolf Rabenseifner wrote: > First, I want to thank all chapter authors for their fine work > cleaning up all the MPI-1/-2 problems and achieving a single monolithic > MPI-2.1 text. > > Dear reviewer, > > to handle about 20 chapters with in average 5 reviews per chapter, > I would like to formalize it: > > On next Monday (Apr. 28, 2008), I would like to ask you whether you can > make the following statement on the chapter(s) you voloteered for reviewing > (I'll ask independently each reviewer on each chapter): > > --------------------------------------------------------------------------- > Chap. ......... of MPI-2.1 Draft Apr. 19, 2008 represents fully and > exactly (as I can overlook) the text that was given by MPI-1.1 (June 1995), > MPI-2 (July 1997), MPI-1 errata (Oct. 12, 1998), Ballot 1+2 (May 15, 2002), > Ballot 3 (protocol from March 2008 meeting, 1st vote), > and Ballot 4 (protocol from March 2008 meeting, official reading) > if the following text-modifications (they are already implemented in the > current draft) are accepted by the MPI Forum: > - XXXXX > and if the following bugs will be corrected until first vote > in June 2008 meeting: > - YYYYY. > Further comments (not official part of this review): > - ZZZZZ > --------------------------------------------------------------------------- > > Please do not use ZZZZZ for MPI-2.2 items or for any further enhancement. > > If there are such XXXXX, YYYYY, and ZZZZZ items, then I can include them > into my slides, if you are sending it to me not later than > > Friday, April 25, 2008. > > All items that you detect later, you may bring to the MPI Forum > with your own slide, plugging in your own laptop at the meeting. > > And same procedure for MPI-1.3 with only MPI-1 input. > > I hope this review process is fine with you. > > Exception: Review of Chap. 3 and 4 will be based on the text > prepared by Rich Graham together with his reviewers this > week, i.e. final reviews at the meeting will be done > on MPI-2.1 Draft Apr. 26, 2008. > > Best regards from travel (currently Salishan conference, USA) > Rolf > > --------------------------------------------------------------------------- > Frontmatter: > - Bill Gropp, Rusty Lusk > Acknowledgements: > - Richard Graham, Bill Gropp, Rusty Lusk > Chap. 1: Introduction to MPI > - Bill Gropp, Rusty Lusk, Karl Feind, Adam Moody, Jesper Traeff > Chap. 2: MPI-2 Terms and Conventions > - Tony Skjellum, Bill Gropp, Richard Barrett, Jesper Traeff > Chap. 3: Point-to-Point Communication > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, > Adam Moody > Chap. 3: Datatypes > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, > Adam Moody > Chap. 5: Collective Communication > - Adam Moody, Steven Ericsson-Zenith, Edgar Gabriel, Rajeev > Thakur, Bill Gropp, Georg Bosilca, Torsten Hoefler, Jesper Traeff Chap. 6: > Groups, Context, and Communicators > - Richard Treumann, Steven Ericsson-Zenith, Edgar Gabriel, Tony > Skjellum, Bill Gropp, Georg Bosilca, Robert Blackmore > Chap. 7: Process Topologies > - Jesper Traeff, Rusty Lusk, Bill Gropp, Richard Barrett > Chap. 8: MPI Environmental Management (incl. sections from MPI-2 Misc.) > - George Bosilca, Rich Graham, Jespar Larsson Traeff, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp > Chap. 9: Miscellany > - Jespar Larsson Traeff, Rich Graham, George Bosilca, > Steve Poole, Kannan Narasimhan, B. Gropp > Chap.10: Process Creation and Management > - David Solt, Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, > Kalem Karian > Chap.11: One-Sided Communication > - Jespar Larsson Traeff, Ericsson-Zenith, Martin Schulz, > Bill Gropp, Darius Buntinas > Chap.12: External Interfaces > - Bronis de Supinski, Bill Gropp > Chap.13: I/O > - Rajeev Thakur, Joachim Worringen, Bill Gropp, Rainer Keller > Chap.14: Profiling Interface > - Bronis de Supinski, Bill Gropp, Jeff Brown > Chap.15: Deprecated Functions > - Rolf Rabenseifner, Bill Gropp > Chap.16: Language Bindings > - Jeff Squyres, Steve Poole, Purushotham Bangalore, > Bill Gropp, Erez Haba, Alexander Supalov > Bibliography: > - Rusty Lusk, Bill Gropp > Annex A: Language Bindings Summary > - Alexander Supalov, Jeff Squyres, Steve Poole, Purushotham > Bangalore, Bill Gropp, > Annex B: Change Log > - Rolf Rabenseifner, Bill Gropp > Index: > - Rusty Lusk, Bill Gropp > > MPI-1.3: Bill Gropp, Rolf Rabenseifner, Adam Moody, Puri Bangalore, > Terry Dontje > > > > > 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 -- ---------------------------------------------------------------- Dipl.-Inf. Rainer Keller http://www.hlrs.de/people/keller HLRS Tel: ++49 (0)711-685 6 5858 Nobelstrasse 19 Fax: ++49 (0)711-685 6 5832 70550 Stuttgart email: keller_at_[hidden] Germany AIM/Skype:rusraink *

1 0

problems with 19 Apr document
by unknown＠example.com 28 Apr '08

28 Apr '08

In reviewing the 19 April document for the Chicago meeting, I found a few issues: Chapter 15 (deprecated functions) - Seems to be missing some deprecated functions: MPI_DUP_FN, MPI_NULL_COPY_FN, MPI_NULL_DELETE_FN (there might be others?). Annex A - p498:41-42: The table header for the 2nd to last table on the page is a little weird: "C Constants specifying ignored input (no C++ or Fortran)", and the constants are MPI_F_STATUS[ES]_IGNORE. So the heading is technically correct, but a little confusing. - p556: this table represents (I think) all MPI-1 functions. Do we need to add in MPI-2 functions? Or do we still need this table anymore, since all the C++ functions are now integrated in the whole document? Examples Index - There are still a bunch of repeated names, some in all caps, some in mixed case, etc. - There are some examples listed just by MPI function name (e.g., MPI_SEND and MPI_Send) -- are we listing every MPI function in every MPI example? How was the selection for these example names given? Constant Index - The first entry is still "MPI::*_NULL" - Are we listing the C++ constants and Fortran constants here, too? Or just the C constants? Or just language neutral? (I only see C++ predefined datatypes listed -- should we list all or none of them?) Declarations Index - I don't see the MPI C++ subtypes (e.g., MPI::Intercomm). Callback function prototype index - C++ types are missing Function index - There are many entries that should not be in this index, because they are not functions. I suspect that someone simply used the wrong latex macro in the text. MPI_ MPI_*_FREE MPI_CHAR MPI_CHARACTER MPI_COMM_NULL MPI_COMM_SELF MPI_COMM_WORLD MPI_DUP_FN MPI_ERROR MPI_ERRORS_RETURN MPI_FILE MPI_FILE_NULL MPI_MAX MPI_STATUS MPI_SUCCESS MPI_THREAD_INIT (!! looks like a typo page p479) MPI_TYPE_UB, MPI_TYPE_LB (these two functions are on one line) MPI_UNSIGNED_CHAR MPI_WCHAR MPI_WIN_BASE MPI_XXX_GET_ERRHANDLER MPI_YYY_DELETE_ATTR MPI_YYY_FREE_KEYVAL MPI_YYY_GET_ATTR MPI_YYY_SET_ATTR -- Jeff Squyres Cisco Systems

1 0

Meeting Apr. 28-30 - MPI-1.3 and MPI-2.1
by unknown＠example.com 27 Apr '08

27 Apr '08

Hi all, latest MPI-1.3 and MPI-2.1 preparation of the meeting is done. All relelant files can be found in the first section of http://www.hlrs.de/mpi/mpi21/doc/ Username and pw as usual: mpi21 I'm leaving now my office and the internet. All further reviews: please have them available on your laptop and (if possible/necessary) a printed version for me. See you on Monday - 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] Formal MPI-2.1 Review
by unknown＠example.com 26 Apr '08

26 Apr '08

Rolf, As you have the write token I didn't want to commit the changes suggested by Kannan. Attached you will find the diff regarding the chapter 8 (inquiry.tex). george. On Apr 26, 2008, at 1:13 PM, Narasimhan, Kannan wrote: > Rolf, > > Apologies for missing the April 25 deadline. I've reviewed Chapters > 8 and 9 in the MPI 2.1 draft, and it looks good -- the authors have > done a wonderful job with the merge. > > Here is the "informal" review statement (since I wasn't sure if my > minor edits fall under XXXX or YYYY category) of the formal > statement :). > > The following is the list of edits required in each of these chapters: > > Chapter 8 ( MPI Environment Management ) > > 1. Pg 265, 8.3 Error Handling (Line 12): Remove the phrase "On the > other hand" and reword the sentence as follows: C and C++ have > distinct typedefs for user defined error handling callback functions > that accept communicator, file, and window arguments. > > 2. Pg 266, 8.3.1 Error Handlers for Communicators (Lines 22-26): > Change all references to HANDLER_FUNCTION to > {COMM,WIN,FILE}_ERRHANDLER_FN in the "Advice to users" para. > > 3. Pg 268, 8.3.2 Error Handlers for Windows (Line 13): ADD: Creates > an error handler that can be attached to a window object. > > 4. Pg 269, 8.3.3 Error Handlers for Files (Line 24): ADD: Creates an > error handler that can be attached to a file object. > > 5. Pg 270, 8.3.4 Freeing Error handlers and Retrieving Error > Strings(Line 27-28): Change the sentence to: The error handler will > be deallocated after all of the objects associated with it > (communicator, window, or file) are deallocated. > > Chapter 9 (Miscellany) > > 1. Pg 283, 9.1 The Info Object (Line 26): Change the first sentence > to: Many of the routines in MPI take an info argument. > > -Kannan- > > > -----Original Message----- > From: mpi-21-bounces_at_[hidden] [mailto:mpi-21-bounces_at_[hidden] > ] On Behalf Of Rolf Rabenseifner > Sent: Monday, April 21, 2008 1:39 PM > To: MPI 2.1 Mailing List > Subject: [Mpi-21] Formal MPI-2.1 Review > > First, I want to thank all chapter authors for their fine work > cleaning up all the MPI-1/-2 problems and achieving a single > monolithic > MPI-2.1 text. > > Dear reviewer, > > to handle about 20 chapters with in average 5 reviews per chapter, I > would like to formalize it: > > On next Monday (Apr. 28, 2008), I would like to ask you whether you > can make the following statement on the chapter(s) you voloteered > for reviewing (I'll ask independently each reviewer on each chapter): > > --------------------------------------------------------------------------- > Chap. ......... of MPI-2.1 Draft Apr. 19, 2008 represents fully and > exactly (as I can overlook) the text that was given by MPI-1.1 (June > 1995), > MPI-2 (July 1997), MPI-1 errata (Oct. 12, 1998), Ballot 1+2 (May 15, > 2002), Ballot 3 (protocol from March 2008 meeting, 1st vote), and > Ballot 4 (protocol from March 2008 meeting, official reading) if the > following text-modifications (they are already implemented in the > current draft) are accepted by the MPI Forum: > - XXXXX > and if the following bugs will be corrected until first vote in June > 2008 meeting: > - YYYYY. > Further comments (not official part of this review): > - ZZZZZ > --------------------------------------------------------------------------- > > Please do not use ZZZZZ for MPI-2.2 items or for any further > enhancement. > > If there are such XXXXX, YYYYY, and ZZZZZ items, then I can include > them into my slides, if you are sending it to me not later than > > Friday, April 25, 2008. > > All items that you detect later, you may bring to the MPI Forum with > your own slide, plugging in your own laptop at the meeting. > > And same procedure for MPI-1.3 with only MPI-1 input. > > I hope this review process is fine with you. > > Exception: Review of Chap. 3 and 4 will be based on the text > prepared by Rich Graham together with his reviewers this > week, i.e. final reviews at the meeting will be done > on MPI-2.1 Draft Apr. 26, 2008. > > Best regards from travel (currently Salishan conference, USA) Rolf > > --------------------------------------------------------------------------- > Frontmatter: > - Bill Gropp, Rusty Lusk > Acknowledgements: > - Richard Graham, Bill Gropp, Rusty Lusk Chap. 1: > Introduction to MPI > - Bill Gropp, Rusty Lusk, Karl Feind, Adam Moody, Jesper > Traeff Chap. 2: MPI-2 Terms and Conventions > - Tony Skjellum, Bill Gropp, Richard Barrett, Jesper Traeff > Chap. 3: Point-to-Point Communication > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt > Koop, > Adam Moody > Chap. 3: Datatypes > - Rich Graham, Jespar Larsson Traeff, George Bosilca, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt > Koop, > Adam Moody > Chap. 5: Collective Communication > - Adam Moody, Steven Ericsson-Zenith, Edgar Gabriel, Rajeev > Thakur, > Bill Gropp, Georg Bosilca, Torsten Hoefler, Jesper Traeff > Chap. 6: Groups, Context, and Communicators > - Richard Treumann, Steven Ericsson-Zenith, Edgar Gabriel, > Tony > Skjellum, Bill Gropp, Georg Bosilca, Robert Blackmore > Chap. 7: Process Topologies > - Jesper Traeff, Rusty Lusk, Bill Gropp, Richard Barrett > Chap. 8: MPI Environmental Management (incl. sections from MPI-2 > Misc.) > - George Bosilca, Rich Graham, Jespar Larsson Traeff, > Steve Poole, Kannan Narasimhan, David Solt, B. Gropp Chap. > 9: Miscellany > - Jespar Larsson Traeff, Rich Graham, George Bosilca, > Steve Poole, Kannan Narasimhan, B. Gropp > Chap.10: Process Creation and Management > - David Solt, Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill > Gropp, > Kalem Karian > Chap.11: One-Sided Communication > - Jespar Larsson Traeff, Ericsson-Zenith, Martin Schulz, > Bill Gropp, Darius Buntinas > Chap.12: External Interfaces > - Bronis de Supinski, Bill Gropp > Chap.13: I/O > - Rajeev Thakur, Joachim Worringen, Bill Gropp, Rainer Keller > Chap.14: Profiling Interface > - Bronis de Supinski, Bill Gropp, Jeff Brown > Chap.15: Deprecated Functions > - Rolf Rabenseifner, Bill Gropp > Chap.16: Language Bindings > - Jeff Squyres, Steve Poole, Purushotham Bangalore, > Bill Gropp, Erez Haba, Alexander Supalov > Bibliography: > - Rusty Lusk, Bill Gropp > Annex A: Language Bindings Summary > - Alexander Supalov, Jeff Squyres, Steve Poole, Purushotham > Bangalore, > Bill Gropp, > Annex B: Change Log > - Rolf Rabenseifner, Bill Gropp > Index: > - Rusty Lusk, Bill Gropp > > MPI-1.3: Bill Gropp, Rolf Rabenseifner, Adam Moody, Puri Bangalore, > Terry Dontje > > > > > 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] Formal MPI-2.1 Review
by unknown＠example.com 26 Apr '08

26 Apr '08

Rolf, Apologies for missing the April 25 deadline. I've reviewed Chapters 8 and 9 in the MPI 2.1 draft, and it looks good -- the authors have done a wonderful job with the merge. Here is the "informal" review statement (since I wasn't sure if my minor edits fall under XXXX or YYYY category) of the formal statement :). The following is the list of edits required in each of these chapters: Chapter 8 ( MPI Environment Management ) 1. Pg 265, 8.3 Error Handling (Line 12): Remove the phrase "On the other hand" and reword the sentence as follows: C and C++ have distinct typedefs for user defined error handling callback functions that accept communicator, file, and window arguments. 2. Pg 266, 8.3.1 Error Handlers for Communicators (Lines 22-26): Change all references to HANDLER_FUNCTION to {COMM,WIN,FILE}_ERRHANDLER_FN in the "Advice to users" para. 3. Pg 268, 8.3.2 Error Handlers for Windows (Line 13): ADD: Creates an error handler that can be attached to a window object. 4. Pg 269, 8.3.3 Error Handlers for Files (Line 24): ADD: Creates an error handler that can be attached to a file object. 5. Pg 270, 8.3.4 Freeing Error handlers and Retrieving Error Strings(Line 27-28): Change the sentence to: The error handler will be deallocated after all of the objects associated with it (communicator, window, or file) are deallocated. Chapter 9 (Miscellany) 1. Pg 283, 9.1 The Info Object (Line 26): Change the first sentence to: Many of the routines in MPI take an info argument. -Kannan- -----Original Message----- From: mpi-21-bounces_at_[hidden] [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of Rolf Rabenseifner Sent: Monday, April 21, 2008 1:39 PM To: MPI 2.1 Mailing List Subject: [Mpi-21] Formal MPI-2.1 Review First, I want to thank all chapter authors for their fine work cleaning up all the MPI-1/-2 problems and achieving a single monolithic MPI-2.1 text. Dear reviewer, to handle about 20 chapters with in average 5 reviews per chapter, I would like to formalize it: On next Monday (Apr. 28, 2008), I would like to ask you whether you can make the following statement on the chapter(s) you voloteered for reviewing (I'll ask independently each reviewer on each chapter): --------------------------------------------------------------------------- Chap. ......... of MPI-2.1 Draft Apr. 19, 2008 represents fully and exactly (as I can overlook) the text that was given by MPI-1.1 (June 1995), MPI-2 (July 1997), MPI-1 errata (Oct. 12, 1998), Ballot 1+2 (May 15, 2002), Ballot 3 (protocol from March 2008 meeting, 1st vote), and Ballot 4 (protocol from March 2008 meeting, official reading) if the following text-modifications (they are already implemented in the current draft) are accepted by the MPI Forum: - XXXXX and if the following bugs will be corrected until first vote in June 2008 meeting: - YYYYY. Further comments (not official part of this review): - ZZZZZ --------------------------------------------------------------------------- Please do not use ZZZZZ for MPI-2.2 items or for any further enhancement. If there are such XXXXX, YYYYY, and ZZZZZ items, then I can include them into my slides, if you are sending it to me not later than Friday, April 25, 2008. All items that you detect later, you may bring to the MPI Forum with your own slide, plugging in your own laptop at the meeting. And same procedure for MPI-1.3 with only MPI-1 input. I hope this review process is fine with you. Exception: Review of Chap. 3 and 4 will be based on the text prepared by Rich Graham together with his reviewers this week, i.e. final reviews at the meeting will be done on MPI-2.1 Draft Apr. 26, 2008. Best regards from travel (currently Salishan conference, USA) Rolf --------------------------------------------------------------------------- Frontmatter: - Bill Gropp, Rusty Lusk Acknowledgements: - Richard Graham, Bill Gropp, Rusty Lusk Chap. 1: Introduction to MPI - Bill Gropp, Rusty Lusk, Karl Feind, Adam Moody, Jesper Traeff Chap. 2: MPI-2 Terms and Conventions - Tony Skjellum, Bill Gropp, Richard Barrett, Jesper Traeff Chap. 3: Point-to-Point Communication - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, Adam Moody Chap. 3: Datatypes - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, Adam Moody Chap. 5: Collective Communication - Adam Moody, Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, Bill Gropp, Georg Bosilca, Torsten Hoefler, Jesper Traeff Chap. 6: Groups, Context, and Communicators - Richard Treumann, Steven Ericsson-Zenith, Edgar Gabriel, Tony Skjellum, Bill Gropp, Georg Bosilca, Robert Blackmore Chap. 7: Process Topologies - Jesper Traeff, Rusty Lusk, Bill Gropp, Richard Barrett Chap. 8: MPI Environmental Management (incl. sections from MPI-2 Misc.) - George Bosilca, Rich Graham, Jespar Larsson Traeff, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp Chap. 9: Miscellany - Jespar Larsson Traeff, Rich Graham, George Bosilca, Steve Poole, Kannan Narasimhan, B. Gropp Chap.10: Process Creation and Management - David Solt, Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, Kalem Karian Chap.11: One-Sided Communication - Jespar Larsson Traeff, Ericsson-Zenith, Martin Schulz, Bill Gropp, Darius Buntinas Chap.12: External Interfaces - Bronis de Supinski, Bill Gropp Chap.13: I/O - Rajeev Thakur, Joachim Worringen, Bill Gropp, Rainer Keller Chap.14: Profiling Interface - Bronis de Supinski, Bill Gropp, Jeff Brown Chap.15: Deprecated Functions - Rolf Rabenseifner, Bill Gropp Chap.16: Language Bindings - Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Erez Haba, Alexander Supalov Bibliography: - Rusty Lusk, Bill Gropp Annex A: Language Bindings Summary - Alexander Supalov, Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Annex B: Change Log - Rolf Rabenseifner, Bill Gropp Index: - Rusty Lusk, Bill Gropp MPI-1.3: Bill Gropp, Rolf Rabenseifner, Adam Moody, Puri Bangalore, Terry Dontje 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

Formal MPI-2.1 Review
by unknown＠example.com 21 Apr '08

21 Apr '08

First, I want to thank all chapter authors for their fine work cleaning up all the MPI-1/-2 problems and achieving a single monolithic MPI-2.1 text. Dear reviewer, to handle about 20 chapters with in average 5 reviews per chapter, I would like to formalize it: On next Monday (Apr. 28, 2008), I would like to ask you whether you can make the following statement on the chapter(s) you voloteered for reviewing (I'll ask independently each reviewer on each chapter): --------------------------------------------------------------------------- Chap. ......... of MPI-2.1 Draft Apr. 19, 2008 represents fully and exactly (as I can overlook) the text that was given by MPI-1.1 (June 1995), MPI-2 (July 1997), MPI-1 errata (Oct. 12, 1998), Ballot 1+2 (May 15, 2002), Ballot 3 (protocol from March 2008 meeting, 1st vote), and Ballot 4 (protocol from March 2008 meeting, official reading) if the following text-modifications (they are already implemented in the current draft) are accepted by the MPI Forum: - XXXXX and if the following bugs will be corrected until first vote in June 2008 meeting: - YYYYY. Further comments (not official part of this review): - ZZZZZ --------------------------------------------------------------------------- Please do not use ZZZZZ for MPI-2.2 items or for any further enhancement. If there are such XXXXX, YYYYY, and ZZZZZ items, then I can include them into my slides, if you are sending it to me not later than Friday, April 25, 2008. All items that you detect later, you may bring to the MPI Forum with your own slide, plugging in your own laptop at the meeting. And same procedure for MPI-1.3 with only MPI-1 input. I hope this review process is fine with you. Exception: Review of Chap. 3 and 4 will be based on the text prepared by Rich Graham together with his reviewers this week, i.e. final reviews at the meeting will be done on MPI-2.1 Draft Apr. 26, 2008. Best regards from travel (currently Salishan conference, USA) Rolf --------------------------------------------------------------------------- Frontmatter: - Bill Gropp, Rusty Lusk Acknowledgements: - Richard Graham, Bill Gropp, Rusty Lusk Chap. 1: Introduction to MPI - Bill Gropp, Rusty Lusk, Karl Feind, Adam Moody, Jesper Traeff Chap. 2: MPI-2 Terms and Conventions - Tony Skjellum, Bill Gropp, Richard Barrett, Jesper Traeff Chap. 3: Point-to-Point Communication - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, Adam Moody Chap. 3: Datatypes - Rich Graham, Jespar Larsson Traeff, George Bosilca, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp, Matt Koop, Adam Moody Chap. 5: Collective Communication - Adam Moody, Steven Ericsson-Zenith, Edgar Gabriel, Rajeev Thakur, Bill Gropp, Georg Bosilca, Torsten Hoefler, Jesper Traeff Chap. 6: Groups, Context, and Communicators - Richard Treumann, Steven Ericsson-Zenith, Edgar Gabriel, Tony Skjellum, Bill Gropp, Georg Bosilca, Robert Blackmore Chap. 7: Process Topologies - Jesper Traeff, Rusty Lusk, Bill Gropp, Richard Barrett Chap. 8: MPI Environmental Management (incl. sections from MPI-2 Misc.) - George Bosilca, Rich Graham, Jespar Larsson Traeff, Steve Poole, Kannan Narasimhan, David Solt, B. Gropp Chap. 9: Miscellany - Jespar Larsson Traeff, Rich Graham, George Bosilca, Steve Poole, Kannan Narasimhan, B. Gropp Chap.10: Process Creation and Management - David Solt, Dries Kimpe, Rusty Lusk, Georg Bosilca, Bill Gropp, Kalem Karian Chap.11: One-Sided Communication - Jespar Larsson Traeff, Ericsson-Zenith, Martin Schulz, Bill Gropp, Darius Buntinas Chap.12: External Interfaces - Bronis de Supinski, Bill Gropp Chap.13: I/O - Rajeev Thakur, Joachim Worringen, Bill Gropp, Rainer Keller Chap.14: Profiling Interface - Bronis de Supinski, Bill Gropp, Jeff Brown Chap.15: Deprecated Functions - Rolf Rabenseifner, Bill Gropp Chap.16: Language Bindings - Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Erez Haba, Alexander Supalov Bibliography: - Rusty Lusk, Bill Gropp Annex A: Language Bindings Summary - Alexander Supalov, Jeff Squyres, Steve Poole, Purushotham Bangalore, Bill Gropp, Annex B: Change Log - Rolf Rabenseifner, Bill Gropp Index: - Rusty Lusk, Bill Gropp MPI-1.3: Bill Gropp, Rolf Rabenseifner, Adam Moody, Puri Bangalore, Terry Dontje 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

All REVIEWERS - Final 1.3 and 2.1 review
by unknown＠example.com 19 Apr '08

19 Apr '08

Dear reviewer, this is the *final* review. http://www.hlrs.de/mpi/mpi21/doc/ is updated with - final version = official reading of MPI-1.3 (hopefully) - official reading version of MPI-2.1 One exception: - The authors and reviewers of Chap. Point-to-Point and Chap. Datatypes may work strongly together to have at the end of the week a version that will have a review at the meeting withou showing further needs. Please, mark errors in your reviews clearly with ERR. Please mark all other stuff with 22 because it will go into MPI-2.2. The resources for MPI-2.1 are now nearly fully consumed. The shortest summary of open issues can be found at http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review-openissues.… Review format - please use: ---------------------------------------------------------------------------------- 1234567890123456789012345678901234567890123456789012345678901234567890123456789012 All references are based on MPI-2.1 Draft Apr. 19, 2008 ww.a __ pnnn.ll text (with nnn=page number and ll=line number text continued ... ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) ---------------------------------------------------------------------------------- PLEASE: - Please check very carefully all red or magenta changes. Modifications are done by the chapter's author (red) or by me (magenta). You may be the first reviewer who read and check this text. - Please check carefully the cyan text. Those modifications are proposed by a reviewer and have been implemented by my You may be the second reviewer for those modifications. - All green stuff should be fine, because it is based on Forum's decisions (Ballot 1-4). - Original text is black (MPI-1.3) or blue (MPI-2.0). Thanks and 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] AUTHORS+REVIEWERS - Draft Apr. 12, 2008
by unknown＠example.com 19 Apr '08

19 Apr '08

Hi Adam, Rolf, > I've marked most of your edits with DON2, which means I've made the > change as you recommended. However, there are a number for which I'm > not clear on what you meant. These are marked with "vv", which points > to the question following. Would you please clarify these items? As a > reference, let's use the following document for page and line numbers: > > http://www.hlrs.de/organization/par/services/models/mpi/mpi21/doc/mpi-repor… > -Adam Thanks Adam! I commented on your comments below. Ah, btw. the page numbers are *not* correct in xpdf (pdf page numbers vs. printed page numbers). Rolf, please add the things we decided to run by the Forum to some ballot for the meeting next week - they should be easy to solve. Thanks! > >general: the line numbers are completely out of sync ... it's hard to > >classify a line that is between two line numbers. This is still ambiguous, but it seems to be a general problem. Why is the font used to number the lines smaller than the text in the lines? > >5.a DON2 EDIT p129.19-41 "all group members" vs. "all members of a group" > > should use the same phrasing (parallel structure) > > > > > >5.b DON2 NICE p129.41 Reference to 5.11 not 5.11.1 > >5.c DON2 EDIT p129.45 remove "," (comma) > >5.d DON2 EDIT p129.43 replace "the same" with "a" > >5.e DON2 EDIT p129.45 "the same group" in line 43 conflicts with "group or > > groups" > > > > > There is not really a clear way to state this. As Rejeev also > suggested, the definition of "matching" is not well understood here. > Perhaps the best option is to remove this statement altogether, since it > is defined in more detail in the "Specifics" sections for intra- and > inter-communicators. I'll remove the statement, but the idea of > "matching" parameters in collective calls should be discussed in the > Forum. Thus, the following lines: > "A collective operation is executed by having all processes in the > same group call the > communication routine, with matching arguments. One of the key > arguments is a communicator ..." > are now written more simply as: > "One of the key arguments in a call to a collective routine is a > communicator ..." ok > >5.f vv CLAR p131.1 add "with exceptions stated in the following" to first > > sentence > > > > > Do you mean exceptions to the matching of datatypes in sender and > receiver? Are there exceptions to this? The expection is for arguments that are only significant at certain processes. I.e., not all arguments must match (because they are ignored). But I guess it's ok and clear as it is - we don't need a change here. > >5.g DON2 EDIT p131.4 no linebreak (Chapter~\ref{...}) > >5.h *NO* ERR p131.31 replace "will" with "might" > > > > > I'd leave this in, since it was the original wording for this version of > the standard. I think there is still an escape here already in the "(or > a similar mechanism)" phrase. I would like to run this by the Forum. Yes, it is the original wording, but some parts of the original wording are not accurate, so we should discuss this. Non-blocking collectives without tags are possible and useful, so why should we say wrong things in the revised version of the standard? And we also do not need "similar mechanisms". I'd say this sentence is misleading. > >5.i vv ERR p132. "special communicator must be created" this is wrong, > > later (in the bcast section) it is stated differently > > ... I would just remove this part of the advice or say > > "might be created" (see Bcast advice) > > > > > Could you specify the particular advice via page and line numbers? It's > not clear to me what you are referring to here. ups, I forgot the line numbers here - sorry! It's line 1-2. It says that implementors need to implement a "special communicator". Nobody does this, most implementations just use special tags. So this advice is also misleading (actually wrong). > >5.j vv CLAR p131.37 add "depending on the operation performed after last > > sentence (right now it sounds like ths user is free to > > choose which argument to replace) > > > > > Do you mean p132.27 instead? The recommendation doesn't seem to line up > with the document I have. yes, this is line 27, got confused with the line numbers here. > >5.k *NO* EDIT p133.32 "a" -> "an"? > > > > > I think "a" is actually appropriate here. hmm, I learned that "an" has to come before words starting with a,e,o,u ... but "a" sounds (flows) much more natural. Don't change it (that's why I added the "?" to my original comment :). > >5.l DON2 EDIT p136.22 start sentence with "If the communicator is an > > intracommunicator" as for all the other operations, > > remove "for intracommunicators" in line 23 > >5.m DON2 EDIT p136.24 replace "," by "and" > >5.n ?? EDIT p136.26-31 this paragraph is redundant (it's all already stated > > earlier, do we want this redundancy in the standard?) > > > > > I agree that it is redundant, but this emphasis in a particular case may > be useful to get the point across. I'd leave it up to the Forum to vote > on this. ok, good idea. > >5.o *NO* EDIT p136.32 move sentence to end of the previous paragraph (line > > 25) > > > > > Although, this text may read more smoothly with this edit, it breaks > symmetry on where the "in place" statements are placed in other > descriptions. ok, I agree. > >5.p *NO* EDIT p136.37 "data is braodcasted" (not braodcast) > > > > > Left as "broadcast" per discussion between Bronis and Torsten which > concluded that "broadcast" is recommended. yes! > >5.q DON2 CLAR p136.38-39 the text talks about send and receive buffer argument, > > but bcast only has a single buffer argument ... > > > > > >5.r ?? CLAR p136.38 "must be consistent with the ..." what does the word > > consistent mean in this context? This seems undefined. > > I think it means that the signature (size, count) is > > the same. We should say this explicitely. The same > > term "consistent" is used in all following operations > > (I'm not going to add it again) > > > > > I agree that "consistent" is not defined, however, I'm not sure what it > means either. I think this change should be left to the Forum. Yes, I'd just say that this needs to be defined. I can only guess what it means. > >5.s DON2 EDIT p138.3 write "all processes" instead of "process i" (i is > > never defined) > > > > > I changed this to: > "The type signature of sendcount, sendtype on each process must be > equal ..." perfect! > >5.t *NO* ERR p139.47 data is not necessarily placed in rank order. The > > order is freely definably by the user in the displs[] > > array. Or does the standard enforce the displs[] array > > to preserve order? We might want to run this through > > the forum (or just ignore it?)? > > > > > I think the "that is, ..." portion of this statement clarifies the meaning. I don't think so. I also discussed this with Jesper who also thinks that this is a controversary statement. Actually, I'd say that the standard forces the displs[] array to be in rank-order. Everything else can be interpreted as an erroneous MPI program. I think we don't want this. But we should run this by the Forum. > >5.u DON2 CLAR p136.42 add "The examples in this section are using > > intracommunicators." as in p140.27 > >5.v ?? EDIT p147.48 the last paragraph is redundant (has been stated > > before for all collectives) > > > > > Again, I'll leave this redundancy question to the Forum. ok > >5.w DON2 EDIT p157.35 why a separate subsection for Alltoallw but not for > > Alltoallv? I'd remove this subsection > >5.x DON2 EDIT p157.36 the first two sentences should go to rationale (we > > don't need to rationalize the operation in the > > description) > > > > > I missed this piece in the original rewrite, and so this section still > required significant editting. I've made it look and feel more like the > AlltoallV definition. great! > >5.y DON2 EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for > > MPI_Reduce" > >5.z vv EDIT p162.13 state that the example is in Fortran (it's said for > > all the C examples before) > > > > > I don't see examples in this chapter that say they are in C either, or > at least, there are many that don't. ok, there are some that do and some that don't. Ah, I don't care ... people who are not able to recognize the language are not our target audience anyway (I hope). > >5.aa DON2 EDIT p163.10-12 I think we don't need to backref to MPI-1 here if we > > consider MPI-2.1 a complete standard. > > > > > Ok, I've been convinced to remove this. :) > >5.ab DON2 CLAR p163.20 replace "bit" by "numeric" or "integer" > >5.ac *NO* EDIT p167.41 doubled sentence "The order of ..." > > > > > The sentence is not technically duplicated. I'll leave this text as is > now, although, I agree that this paragraph could be rewritten to state > its point more clearly. "The order of evaluation can be changed, talking advantage of the associativity of the operation. If commute = true then the order of evaluation can be changed" ... ok, I see. It sounds like double. I'd still re-phrase this into a single sentence, such as: "If commute = true, then the order of evaluation can be changed, talking advantage of the associativity of the operation." > >5.ad DON2 CLAR p169.2 add: (without supporting the "in place" option) > >5.ae DON2 ERR p169.16-20 the example will deadlock if root == groupsize-1. Has > > been there for a while :). Use Irecv/Wait instead. > >5.af vv EDIT p171.48 state that example is in Fortran > > > > > Again, not sure if this needs to be done? agree - please ignore this > >5.ag DON2 ERR p174.12-20 this rationale should be erased completely because it > > explains (for MPI-1), why only the inclusive is supported ;-) > >5.ah DON2 ERR p175.20 erase the last sentence in rationale, we don't need > > this anymore (is MPI-1) > >5.ai ?? EDIT p177.48 move orphaned Example header to next page (might > > change after edits though -> check chapter for orphans) > >5.aj ?? EDIT p179.24 the font suddenly changes? (sans-serif) > > > > > Haven't checked these two in the recent document. I suppose some of the > checks will need to wait until the final copy is available for reading. yes, I just wanted to remind us to do it at the end. > >5.ak ?? CLAR p179.27 maybe we should add: "and to ensure appropriate > > matching (for deterministic behavior) > > > > > I'll leave this one to the Forum. ok Thanks & Best, Torsten -- bash$ :(){ :|:&};: --------------------- http://www.unixer.de/ ----- Indiana University | http://www.indiana.edu Open Systems Lab | http://osl.iu.edu/ 150 S. Woodlawn Ave. | Bloomington, IN, 474045-7104 | USA Lindley Hall Room 135 | +01 (812) 855-3608

1 0

AUTHORS - write token is back at me (except pt2pt + datatypes)
by unknown＠example.com 19 Apr '08

19 Apr '08

All authors (except Rich [pt2pt and datatypes]), the write toke is now back at me. Please do *not* further modify the source. I'll finish the MPI-1.3 and MPI 2.1 and I'll put the final version for review on the web in the next hours. Exception: Rich and Co. will work on pt2pt.tex and datatypes.tex the next week together with the reviewers to finish these two chapters also until the meeting. Best regards (next mail with pdf-on-web will come in a few hours) 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] AUTHORS+REVIEWERS - Draft Apr. 12, 2008
by unknown＠example.com 18 Apr '08

18 Apr '08

Hi Torsten, I've marked most of your edits with DON2, which means I've made the change as you recommended. However, there are a number for which I'm not clear on what you meant. These are marked with "vv", which points to the question following. Would you please clarify these items? As a reference, let's use the following document for page and line numbers: http://www.hlrs.de/organization/par/services/models/mpi/mpi21/doc/mpi-repor… -Adam Torsten Hoefler wrote: >Hi Rolf, Adam, >I understand from your mail Rolf, that Adam lost his write token and >that only you can apply the changes/comments to the chapter (in my case >the collectives chapter). Thus, I'll send my review results to the list >instead the chapter author directly. My general comment: very well done >Adam :). > >I have some smaller editing remarks and also found some small errors and >clarification possibilities (see below). > > > >>---------------------------------------------------------------------------------- >>1234567890123456789012345678901234567890123456789012345678901234567890123456789012 >> All references are based on MPI-2.1 Draft Apr. 12, 2008 >>ww.a __ pnnn.ll text (with nnn=page number and ll=line number >> text continued >> ... >>ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) >>---------------------------------------------------------------------------------- >> >> >Ok, here my remarks, many of them (especially EDIT or CLAR) can probably >be ignored, but I thought I'd bring it up: > >general: the line numbers are completely out of sync ... it's hard to >classify a line that is between two line numbers. > >5.a DON2 EDIT p129.19-41 "all group members" vs. "all members of a group" > should use the same phrasing (parallel structure) > > >5.b DON2 NICE p129.41 Reference to 5.11 not 5.11.1 >5.c DON2 EDIT p129.45 remove "," (comma) >5.d DON2 EDIT p129.43 replace "the same" with "a" >5.e DON2 EDIT p129.45 "the same group" in line 43 conflicts with "group or > groups" > > There is not really a clear way to state this. As Rejeev also suggested, the definition of "matching" is not well understood here. Perhaps the best option is to remove this statement altogether, since it is defined in more detail in the "Specifics" sections for intra- and inter-communicators. I'll remove the statement, but the idea of "matching" parameters in collective calls should be discussed in the Forum. Thus, the following lines: "A collective operation is executed by having all processes in the same group call the communication routine, with matching arguments. One of the key arguments is a communicator ..." are now written more simply as: "One of the key arguments in a call to a collective routine is a communicator ..." >5.f vv CLAR p131.1 add "with exceptions stated in the following" to first > sentence > > Do you mean exceptions to the matching of datatypes in sender and receiver? Are there exceptions to this? >5.g DON2 EDIT p131.4 no linebreak (Chapter~\ref{...}) >5.h *NO* ERR p131.31 replace "will" with "might" > > I'd leave this in, since it was the original wording for this version of the standard. I think there is still an escape here already in the "(or a similar mechanism)" phrase. >5.i vv ERR p132. "special communicator must be created" this is wrong, > later (in the bcast section) it is stated differently > ... I would just remove this part of the advice or say > "might be created" (see Bcast advice) > > Could you specify the particular advice via page and line numbers? It's not clear to me what you are referring to here. >5.j vv CLAR p131.37 add "depending on the operation performed after last > sentence (right now it sounds like ths user is free to > choose which argument to replace) > > Do you mean p132.27 instead? The recommendation doesn't seem to line up with the document I have. >5.k *NO* EDIT p133.32 "a" -> "an"? > > I think "a" is actually appropriate here. >5.l DON2 EDIT p136.22 start sentence with "If the communicator is an > intracommunicator" as for all the other operations, > remove "for intracommunicators" in line 23 >5.m DON2 EDIT p136.24 replace "," by "and" >5.n ?? EDIT p136.26-31 this paragraph is redundant (it's all already stated > earlier, do we want this redundancy in the standard?) > > I agree that it is redundant, but this emphasis in a particular case may be useful to get the point across. I'd leave it up to the Forum to vote on this. >5.o *NO* EDIT p136.32 move sentence to end of the previous paragraph (line > 25) > > Although, this text may read more smoothly with this edit, it breaks symmetry on where the "in place" statements are placed in other descriptions. >5.p *NO* EDIT p136.37 "data is braodcasted" (not braodcast) > > Left as "broadcast" per discussion between Bronis and Torsten which concluded that "broadcast" is recommended. >5.q DON2 CLAR p136.38-39 the text talks about send and receive buffer argument, > but bcast only has a single buffer argument ... > > >5.r ?? CLAR p136.38 "must be consistent with the ..." what does the word > consistent mean in this context? This seems undefined. > I think it means that the signature (size, count) is > the same. We should say this explicitely. The same > term "consistent" is used in all following operations > (I'm not going to add it again) > > I agree that "consistent" is not defined, however, I'm not sure what it means either. I think this change should be left to the Forum. >5.s DON2 EDIT p138.3 write "all processes" instead of "process i" (i is > never defined) > > I changed this to: "The type signature of sendcount, sendtype on each process must be equal ..." >5.t *NO* ERR p139.47 data is not necessarily placed in rank order. The > order is freely definably by the user in the displs[] > array. Or does the standard enforce the displs[] array > to preserve order? We might want to run this through > the forum (or just ignore it?)? > > I think the "that is, ..." portion of this statement clarifies the meaning. >5.u DON2 CLAR p136.42 add "The examples in this section are using > intracommunicators." as in p140.27 >5.v ?? EDIT p147.48 the last paragraph is redundant (has been stated > before for all collectives) > > Again, I'll leave this redundancy question to the Forum. >5.w DON2 EDIT p157.35 why a separate subsection for Alltoallw but not for > Alltoallv? I'd remove this subsection >5.x DON2 EDIT p157.36 the first two sentences should go to rationale (we > don't need to rationalize the operation in the > description) > > I missed this piece in the original rewrite, and so this section still required significant editting. I've made it look and feel more like the AlltoallV definition. >5.y DON2 EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for > MPI_Reduce" >5.z vv EDIT p162.13 state that the example is in Fortran (it's said for > all the C examples before) > > I don't see examples in this chapter that say they are in C either, or at least, there are many that don't. >5.aa DON2 EDIT p163.10-12 I think we don't need to backref to MPI-1 here if we > consider MPI-2.1 a complete standard. > > Ok, I've been convinced to remove this. >5.ab DON2 CLAR p163.20 replace "bit" by "numeric" or "integer" >5.ac *NO* EDIT p167.41 doubled sentence "The order of ..." > > The sentence is not technically duplicated. I'll leave this text as is now, although, I agree that this paragraph could be rewritten to state its point more clearly. >5.ad DON2 CLAR p169.2 add: (without supporting the "in place" option) >5.ae DON2 ERR p169.16-20 the example will deadlock if root == groupsize-1. Has > been there for a while :). Use Irecv/Wait instead. >5.af vv EDIT p171.48 state that example is in Fortran > > Again, not sure if this needs to be done? >5.ag DON2 ERR p174.12-20 this rationale should be erased completely because it > explains (for MPI-1), why only the inclusive is supported ;-) >5.ah DON2 ERR p175.20 erase the last sentence in rationale, we don't need > this anymore (is MPI-1) >5.ai ?? EDIT p177.48 move orphaned Example header to next page (might > change after edits though -> check chapter for orphans) >5.aj ?? EDIT p179.24 the font suddenly changes? (sans-serif) > > Haven't checked these two in the recent document. I suppose some of the checks will need to wait until the final copy is available for reading. >5.ak ?? CLAR p179.27 maybe we should add: "and to ensure appropriate > matching (for deterministic behavior) > > I'll leave this one to the Forum. >Best, > Torsten > > > *

1 0