From rabenseifner at [hidden] Tue Apr 1 09:55:35 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 01 Apr 2008 16:55:35 +0200 Subject: [Mpi-21] New version MPI-2.1 April 1, 2008 Message-ID: Dear all, the new version MPI-2.1 Draft April 1, 2008 on http://www.hlrs.de/mpi/mpi21/ --> doc will be the basis for all chapter authors together with their chapter reviewer group. The new version includes all MPI 1.3, MPI 2.0, Errata, Ballots 1-4 and all 22 reviews (until May 28)! The other files will be updated soon. - All deprecated functions are moved into an extra chapter. - Change-log is done. - A draft of the credits is done (still without the e-mail authors of the ballots). - List of figures and tables are done. - Content of the index is corrected (the formatting is still to be done; TYPEDEF: must be revisited; EXAMPLES: are references to all examples; with CONST:, only CONST:MPI... will be used, all other CONST:... will be removed; all parts will get separate sections.) - Additional short subsection "Background of MPI-1.3 and MPI-2.1 If you are a chapter author, you can already print you chapter. The next step will hand over the source code and the write token to the chapter authors. 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) From bronis at [hidden] Tue Apr 1 10:23:30 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Tue, 1 Apr 2008 08:23:30 -0700 (PDT) Subject: [Mpi-21] New version MPI-2.1 April 1, 2008 In-Reply-To: Message-ID: Rolf: Re: > the new version MPI-2.1 Draft April 1, 2008 > on http://www.hlrs.de/mpi/mpi21/ --> doc > will be the basis for all chapter authors together with > their chapter reviewer group. Can you send the list of chapter authors and reviewers? I know that I volunteered to do two chapters but I am not certain which ones. I don't want to get that wrong... Thanks, Bronis > The new version includes all MPI 1.3, MPI 2.0, Errata, Ballots 1-4 > and all 22 reviews (until May 28)! The other files will be updated soon. > - All deprecated functions are moved into an extra chapter. > - Change-log is done. > - A draft of the credits is done (still without the e-mail authors > of the ballots). > - List of figures and tables are done. > - Content of the index is corrected > (the formatting is still to be done; > TYPEDEF: must be revisited; EXAMPLES: are references to all examples; > with CONST:, only CONST:MPI... will be used, > all other CONST:... will be removed; > all parts will get separate sections.) > - Additional short subsection "Background of MPI-1.3 and MPI-2.1 > > If you are a chapter author, you can already print you chapter. > > The next step will hand over the source code and the > write token to the chapter authors. > > 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.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > From rabenseifner at [hidden] Tue Apr 1 10:27:22 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 01 Apr 2008 17:27:22 +0200 Subject: [Mpi-21] CHAPTER Authors and more Message-ID: Dear chapter author, please reload the http://www.hlrs.de/mpi/mpi21/doc/ Tomorrow morning (European time) I will send you all additional information and the access information to the sources. If you see that changes are necessary to achieve the goal - one consistent MPI-2.1 text we will have a very tight schedule: On April 11, your round must be finished and on April 12, the draft version (I'll run latex over the whole doc) for the reviews (and the reading at the Forum meeting) will be done. I cannot do it later, because I'll be on travel. There will be only one additional chance for rannung whole latex again: Small correction based on reviewer comments can be added upto April 18. On April 19, the final version (running latex) for the final review and the official reading at the Forum meeting will be done. Goal: Only small need for discussions at the meeting. All changes to the April 19 version must be finished at the Forum meeting. After the meeting, final official version that will be voted twice (June, Sept.) and will be published at the EuroPVM/MPI'08 ! Best regards Rolf PS: Not more today, because i have to leave my office now. 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) From traff at [hidden] Wed Apr 2 02:36:08 2008 From: traff at [hidden] (Jesper Larsson Traeff) Date: Wed, 2 Apr 2008 09:36:08 +0200 Subject: [Mpi-21] Comments on merged MPI-2.1 document (as per March meeting) In-Reply-To: Message-ID: <20080402073608.GA32765@fourier.it.neclab.eu> Dear All, here are my belated comments to the merged MPI 1.2/PI 2.0 document as per of the Chicago Forum. Hope they are still useful, perhaps to the chapter editors. A lot of the typos and suggestions apply also to the already passed MPI 1.3 and MPI 2.1 documents, which I'm afraid are finalized now? Especially in the parts concerning the "old", "MPI-1" functionality, there is, in my opinion, quite a lot to be done for the document to work, as was also discussed at the meeting (deprecation of deprecated functions, C++ bindings, MPI-1.2 <-> MPI-2 contradictions, ...). In addition to what has been said, it would be good if some of us could take the time to make sure the examples are correct, effective (in getting the point across - some are very long, and somewhat hurried), and do not use deprecated functionality (there's a remark on p.25 that the examples have not been checked and verified - do we want this?). Now that this merge is being done, I think it is important that it will be done well, and we should take the time for this. Best regards Jesper Two general consistency things: 0. count, rank, tag - should be "(nonnegative integer)" in all interface specs (in one-sided it is usually so, in pt2pt sometimes so, sometimes just "(integer)" 1. Is is "high quality" or "high-quality"? ii, 15: [TYPO]: documnts -> documents Chapter 1: [COMM]: In general all the contrasting of MPI-1/MPI-2 reads very awkward. Eg. Section 1.2 should be completely eliminated. p.1,l.28 [TYPO]: "[8,7]" -> "[7,8]" (refs in ascending order) p.3,l.16 [TYPO]: Ref to Chapter 3 is wrong p.4,l.13 [SUGG]: Drop "With this version of MPI..." p.5,l.26 [TYPO]: Capitalize \textit{send} -> \textit{Send} p.6,l.1 [SUGG]: "remove" -> "complement" p.7,l.27 [ADD]: Reference to Appendix of Deprecated Functions (as discussed at Forum meeting) p.7,l.29 [TYPE]: repeats line 26, drop p.6,l.35ff [COMM]: The things of JOD that are now in the standard should be removed from this discussion. Chapter 2: p.9,l.16 [SUGG]: Eliminate MPI-1/MPI-2 distinctions, e.g. "MPI Terms and Conventions Chapter" p.12,l.29 [SUGG]: Make a reference to definition of typemap (Section 3.12, p.75) p.14,l.36 [SUGG]: shouldn't "inquery function" be "query function"? p.16,l.24 [TYPO]: "principle" -> "principal" p.22,l.23 [TYPO]: "a MIMD style" -> "an MIMD style" (?) p.25,l.9 [QUESTION]: Do we really want to stand by this, that the examples have "not been carefully checked or verified"??? Chapter 3: [SUGG]: Change the examples (p.27; 3.2, 3.3, 3.4 etc.) such that they'll work for any number of processes, eg. make explicit what both ranks do if (myrank == 0) { ... } else if (myrank == 1) { ... } At least, examples should be consistent, some of the Fortran examples (as in 3.6) mention what rank .EQ. 1 does [SUGG]: for count, rank, tag arguments, change "(integer)" to "(nonnegative integer)" in all functions descriptions. At least, it should be consistent, which ii now not the case p.27,l.21 [SUGG]: shouldn't this be "Example 3.1"? p.28,l.5 [SUGG]: "(myrank ==1)" reads badly, since it is not in the example; make an explicit if-clause (see above) p.28,l.29 [COMM]: here count is "(nonnegative integer)", but this disappears later, eg. in RECV, p.32,l.4 p.28,l.33,34 [SUGG]: change "(integer)" to "(nonnegative integer)" for dest and tag arguments (and throughout) p.29, Tables should contain all (MPI-1 and MPI-2) datatypes. p.30 [SLIP]: MPI_LONG_LONG has disappeared p.46,l.28 [QUESTION]: Does the Forum realy want to stand to this (recommendation, almost, of unsafe programming style)?? p.53,l.29 [SLIP]: drop this line "Section on Argument and register optimization" (similar is elsewhere, seems an edition slip, eg. p.72,l.32) p.54,l.15: take line up after "(" p.58,l.29-30: state explicitly that count is a "(nonnegative integer)". Same in all array_of_request functions p.59,l.35 [QUESTION]: or is it intended that WAITSOME/TESTSOME takes an array of atleast one request? p.71,l.7-8: change font of MPI_ANY_SOURCE to sf p.76,l.39 [SUGG]: "New Datatype ..." -> "Additional Datatype..." p.87,l.1,2,11 [TYPO]: n-dimensional -> $n$-dimensional (or other consistent font) p.94,l.22: replace deprecated MPI_Address by MPI_Get_address p.94,l.45 [TYPO]: refs are wrong p.97,l.2 [SUGG]: for "gather" put forward reference to Chapter 4 p.99,l.32 [TYPO]: "a argument" -> "an argument" p.103,l.32 [SUGG]: "ELSE" -> "ELSE IF (rank.EQ.1)" p.107,l29 [SUGG]: This example (3.36) could be broken up into smaller examples p.117,l.22 [SUGG]: change "else /* myrank == 1 */" into the explicit "else if (myrank == 1)" (general suggestion) p.117,l.41 [TYPO]: concatenate all -> concatenates all Chapter 4: This chapter does not work in the merged form. p.121,l.48 [TYPO]: "Such processes are called the root" -> "Such a process is called the root" p.125,l.3 [TYPO]: MPI_Exscan is missing p.125,l.35 [TYPO]: drop this line on MPI_Alltoallw p.125,l.47 [SUGG]: "additions" is not the right word here (whole section is VERY problematic, as is this whole chapter) p.127,l.2 [SUGG]: "being identical" must be rephrased p.128,l.19 [SUGG]: all count arguments explicitly "(nonnegative integer)" p.132,l.82 [TYPO]: left justify closing "}" p.135,l.40 [TYPO]: "that that" -> "that" p.144,l.43 [TYPO]: "The jth block of data sent" -> "The block of data sent" p.151,l.27 [SUGG]: "and a scan (parallel prefix) operation." -> "and two scan (parallel prefix) operations." p.152,l.38 [TYPO]: join lines up p.153,l.5-6 [TYPO]: remove '' p.153,l.20 [SUGG]: include MPI_EXSCAN p.153,l.33-34 [SUGG]: "xor" -> "exclusive or" p.153,l.43ff [TYPO]: format table properly p.159,l.160 [SUGG]: add MPI_EXSCAN to list p.160,l.34 [TYPO]: "len" in sf font p.161,l.20ff [TYPO]: RECV, SEND -> MPI_Recv, MPI_Send + add MPI_Comm_size/rank calls to example to set groupsize and rank variables p.161,l.35 [TYPO]: group-size -> groupsize p.163,l.15 [TYPO]: "MPI includes variants..." -> "MPI includes a variant of the reduce operation" p.163,l.45ff [TYPO]: description of MPI_IN_PLACE has been corrected? p.164,l.31 [TYPO]: "MPI includes variants..." -> "MPI includes a variant of the reduce operation..." p.166,l.14ff [SUGG]: drop this rationale, since MPI_EXSCAN has now been included p.166,l.28 [TYPO]: drop p.170,l.22 [COMMENT]: In my opinion, this example is NOT correct (the second scenario may hang, process 1 can enter the Bcast which cannot complete before process 2 enters Bcast, which it cannot before the Send has completed - as in example 4.25) Chapter 5: This chapter does not work in the merged form. [SUGG]: since the chapter deals also with caching on windows and other objects, change title to "Groups, contexts, and caching" p.175,l.18 [SUGG]: "dealt with so far"... is no longer true p.175,l.38-39 [SUGG]: obviously drop lines on no collectives on intercomms p.177,l.10 [SUGG]: drop parenthetical remark p.177,l.19 [SUGG]: drop ref to next chapter p.184,l.22-23 [QUESTION]: Is this advice to implementers needed anymore? p.184,l.46-47 [SUGG]: drop parenthetical remark p.186,l.20-22 [SUGG]: drop, obviously p.190,l.26 [QUESTION]: parenthetical remarks seems strange, drop? p.193,l.7 [TYPO]: "the debugging" -> "a debugging" p.199,l.28 [SUGG]: "the above examples is really three examples" - why not split? The example is too long p.200,l.28 [TYPO]: drop "Advice to users:" (twice) p.200,l.48 [TYPO]: Obviously drop p.201,l.19 [SUGG]: "A group is represented" -> "A group can be represented" p.201,l.38 [QUESTION]: what does "the same algorithm is appropriate..." mean? p.205, Exsample 1 [SUGG]: very long... p.208,l.22 [TYPO]: remove blank space, line tags up. Example is excessively long! p.212,l.44 [SUGG]: "you" does not read well, "one can" or sth. p.212,l.45 [SUGG]: the other extreme would be not to allow it at all... p.213,l.8 [TYPO]: "attributes are attached to communicators" is now wrong p.213,l.23 [TYPO]: represents -> requires p.217,l.40 [TYPO]: formatting, move lines up p.219,l.46 [TYPO]: "the the" -> "then the" Chapter 6: p.231,l.47 [SUGG]: remove "tremendous" p.232,l.17 [SUGG]: remove PARMACS rationale, seems obsolete nowadays p.233,l.19 [SUGG]: remove EXPRESS/PARMACS rationale Chapter 7: p.249,l.5 [SUGG]: "for C" -> "for C and C++" p.261-262 [SUGG]: move MPI-2 errir classes into running discussion/tables Chapter 8: [SUGG] Rename chapter to "Controlling the functionality: The info object" or something like this. Any better/good suggestions? p.271,l.14 [SUGG]: Remove this line p.274,l.36 [TYPO]: change font in (key,value) to sf. Also elsewhere p.275,l.5 [TYPO]: font p.276,l.37 [TYPO]: font should be $n$th Chapter 9: p.279,l.21ff [TYPO]: Remove/reformulate this historical/anecdotical remark Chapter 10: p.312,l.15 [COMM]: Note that here it is said that counts are "(nonnegative integers)"; same should be done also for p2p and collectives, also for consistency reasons. p.313,l.29,l.32 [QUESTION]: is it "high quality" or "high-quality"? p.315,l.11 [TYPO]: MPI_TYPE_EXTENT -> MPI_TYPE_GET_EXTENT (also in next examples) p.330,l.10 [QUESTION]: what is the state of Fortran compilers at this time of writing? Chapter 11: Chapter 12: p.432,l.27 [SUGG]: Make reference to subarray constructor definition, 3.12.4, p.86 Chapter 13: p.435,l.24 [SUGG]: modify, only "MPI" p.436,l.13 [SUGG]: "as of writing" - this state of affairs has changed Chapter 14: p.482,l.27 [SUGG]: Section 14.6 can be dropped? From rabenseifner at [hidden] Wed Apr 2 07:51:37 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Wed, 02 Apr 2008 14:51:37 +0200 Subject: [Mpi-21] Comments on merged MPI-2.1 document (as per March meeting) In-Reply-To: <20080402073608.GA32765@fourier.it.neclab.eu> Message-ID: Jepser, thank you for your detailed review. I expect, that I have to hand over all larger suggestions to the chapter authors and the typos may be handled after the official reading. Best regards Rolf On Wed, 2 Apr 2008 09:36:08 +0200 Jesper Larsson Traeff wrote: > > Dear All, > > here are my belated comments to the merged MPI 1.2/PI 2.0 document as > per of the Chicago Forum. Hope they are still useful, perhaps to the > chapter editors. A lot of the typos and suggestions apply also to the > already passed MPI 1.3 and MPI 2.1 documents, which I'm afraid are > finalized now? Especially in the parts concerning the "old", "MPI-1" > functionality, there is, in my opinion, quite a lot to be done for the > document to work, as was also discussed at the meeting (deprecation of > deprecated functions, C++ bindings, MPI-1.2 <-> MPI-2 contradictions, > ...). In addition to what has been said, it would be good if some of > us could take the time to make sure the examples are correct, > effective (in getting the point across - some are very long, and > somewhat hurried), and do not use deprecated functionality (there's a > remark on p.25 that the examples have not been checked and verified - > do we want this?). Now that this merge is being done, I think it is > important that it will be done well, and we should take the time for > this. > > Best regards > > Jesper > > Two general consistency things: > 0. > count, rank, tag - should be "(nonnegative integer)" in all interface specs > (in one-sided it is usually so, in pt2pt sometimes so, sometimes just > "(integer)" > 1. > Is is "high quality" or "high-quality"? > > ii, 15: > [TYPO]: documnts -> documents > > Chapter 1: > [COMM]: In general all the contrasting of MPI-1/MPI-2 reads very > awkward. Eg. Section 1.2 should be completely eliminated. > p.1,l.28 [TYPO]: "[8,7]" -> "[7,8]" (refs in ascending order) > p.3,l.16 [TYPO]: Ref to Chapter 3 is wrong > p.4,l.13 [SUGG]: Drop "With this version of MPI..." > p.5,l.26 [TYPO]: Capitalize \textit{send} -> \textit{Send} > p.6,l.1 [SUGG]: "remove" -> "complement" > p.7,l.27 [ADD]: Reference to Appendix of Deprecated Functions (as discussed > at Forum meeting) > p.7,l.29 [TYPE]: repeats line 26, drop > p.6,l.35ff [COMM]: The things of JOD that are now in the standard should be > removed from this discussion. > > Chapter 2: > p.9,l.16 [SUGG]: Eliminate MPI-1/MPI-2 distinctions, e.g. "MPI Terms and > Conventions Chapter" > p.12,l.29 [SUGG]: Make a reference to definition of typemap (Section 3.12, > p.75) > p.14,l.36 [SUGG]: shouldn't "inquery function" be "query function"? > p.16,l.24 [TYPO]: "principle" -> "principal" > p.22,l.23 [TYPO]: "a MIMD style" -> "an MIMD style" (?) > p.25,l.9 [QUESTION]: Do we really want to stand by this, that the examples > have "not been carefully checked or verified"??? > > Chapter 3: > [SUGG]: Change the examples (p.27; 3.2, 3.3, 3.4 etc.) such that they'll work > for any number of processes, eg. make explicit what both ranks do > > if (myrank == 0) { > ... > } else if (myrank == 1) { > ... > } > > At least, examples should be consistent, some of the Fortran examples > (as in 3.6) mention what rank .EQ. 1 does > [SUGG]: for count, rank, tag arguments, change "(integer)" to > "(nonnegative integer)" in all functions descriptions. At least, it > should be consistent, which ii now not the case > > p.27,l.21 [SUGG]: shouldn't this be "Example 3.1"? > p.28,l.5 [SUGG]: "(myrank ==1)" reads badly, since it is not in the > example; make an explicit if-clause (see above) > p.28,l.29 [COMM]: here count is "(nonnegative integer)", but this > disappears later, eg. in RECV, p.32,l.4 > p.28,l.33,34 [SUGG]: change "(integer)" to "(nonnegative integer)" for > dest and tag arguments (and throughout) > p.29, Tables should contain all (MPI-1 and MPI-2) datatypes. > p.30 [SLIP]: MPI_LONG_LONG has disappeared > p.46,l.28 [QUESTION]: Does the Forum realy want to stand to this > (recommendation, almost, of unsafe programming style)?? > p.53,l.29 [SLIP]: drop this line "Section on Argument and register > optimization" (similar is elsewhere, seems an edition slip, eg. p.72,l.32) > p.54,l.15: take line up after "(" > p.58,l.29-30: state explicitly that count is a "(nonnegative integer)". > Same in all array_of_request functions > p.59,l.35 [QUESTION]: or is it intended that WAITSOME/TESTSOME takes > an array of atleast one request? > p.71,l.7-8: change font of MPI_ANY_SOURCE to sf > p.76,l.39 [SUGG]: "New Datatype ..." -> "Additional Datatype..." > p.87,l.1,2,11 [TYPO]: n-dimensional -> $n$-dimensional (or other consistent > font) > p.94,l.22: replace deprecated MPI_Address by MPI_Get_address > p.94,l.45 [TYPO]: refs are wrong > p.97,l.2 [SUGG]: for "gather" put forward reference to Chapter 4 > p.99,l.32 [TYPO]: "a argument" -> "an argument" > p.103,l.32 [SUGG]: "ELSE" -> "ELSE IF (rank.EQ.1)" > p.107,l29 [SUGG]: This example (3.36) could be broken up into smaller > examples > p.117,l.22 [SUGG]: change > "else /* myrank == 1 */" > into the explicit > "else if (myrank == 1)" > (general suggestion) > p.117,l.41 [TYPO]: concatenate all -> concatenates all > > Chapter 4: This chapter does not work in the merged form. > p.121,l.48 [TYPO]: "Such processes are called the root" -> "Such a process > is called the root" > p.125,l.3 [TYPO]: MPI_Exscan is missing > p.125,l.35 [TYPO]: drop this line on MPI_Alltoallw > p.125,l.47 [SUGG]: "additions" is not the right word here (whole section is > VERY problematic, as is this whole chapter) > p.127,l.2 [SUGG]: "being identical" must be rephrased > p.128,l.19 [SUGG]: all count arguments explicitly "(nonnegative integer)" > p.132,l.82 [TYPO]: left justify closing "}" > p.135,l.40 [TYPO]: "that that" -> "that" > p.144,l.43 [TYPO]: "The jth block of data sent" -> "The block of data sent" > p.151,l.27 [SUGG]: "and a scan (parallel prefix) operation." -> "and > two scan (parallel prefix) operations." > p.152,l.38 [TYPO]: join lines up > p.153,l.5-6 [TYPO]: remove '' > p.153,l.20 [SUGG]: include MPI_EXSCAN > p.153,l.33-34 [SUGG]: "xor" -> "exclusive or" > p.153,l.43ff [TYPO]: format table properly > p.159,l.160 [SUGG]: add MPI_EXSCAN to list > p.160,l.34 [TYPO]: "len" in sf font > p.161,l.20ff [TYPO]: RECV, SEND -> MPI_Recv, MPI_Send + add MPI_Comm_size/rank > calls to example to set groupsize and rank variables > p.161,l.35 [TYPO]: group-size -> groupsize > p.163,l.15 [TYPO]: "MPI includes variants..." -> "MPI includes a variant of > the reduce operation" > p.163,l.45ff [TYPO]: description of MPI_IN_PLACE has been corrected? > p.164,l.31 [TYPO]: "MPI includes variants..." -> "MPI includes a variant > of the reduce operation..." > p.166,l.14ff [SUGG]: drop this rationale, since MPI_EXSCAN has now been > included > p.166,l.28 [TYPO]: drop > p.170,l.22 [COMMENT]: In my opinion, this example is NOT correct (the > second scenario may hang, process 1 can enter the Bcast which cannot > complete before process 2 enters Bcast, which it cannot before the Send > has completed - as in example 4.25) > > Chapter 5: This chapter does not work in the merged form. [SUGG]: since > the chapter deals also with caching on windows and other objects, change > title to > "Groups, contexts, and caching" > p.175,l.18 [SUGG]: "dealt with so far"... is no longer true > p.175,l.38-39 [SUGG]: obviously drop lines on no collectives on intercomms > p.177,l.10 [SUGG]: drop parenthetical remark > p.177,l.19 [SUGG]: drop ref to next chapter > p.184,l.22-23 [QUESTION]: Is this advice to implementers needed anymore? > p.184,l.46-47 [SUGG]: drop parenthetical remark > p.186,l.20-22 [SUGG]: drop, obviously > p.190,l.26 [QUESTION]: parenthetical remarks seems strange, drop? > p.193,l.7 [TYPO]: "the debugging" -> "a debugging" > p.199,l.28 [SUGG]: "the above examples is really three examples" - why not > split? The example is too long > p.200,l.28 [TYPO]: drop "Advice to users:" (twice) > p.200,l.48 [TYPO]: Obviously drop > p.201,l.19 [SUGG]: "A group is represented" -> "A group can be represented" > p.201,l.38 [QUESTION]: what does "the same algorithm is appropriate..." mean? > p.205, Exsample 1 [SUGG]: very long... > p.208,l.22 [TYPO]: remove blank space, line tags up. Example is excessively > long! > p.212,l.44 [SUGG]: "you" does not read well, "one can" or sth. > p.212,l.45 [SUGG]: the other extreme would be not to allow it at all... > p.213,l.8 [TYPO]: "attributes are attached to communicators" is now wrong > p.213,l.23 [TYPO]: represents -> requires > p.217,l.40 [TYPO]: formatting, move lines up > p.219,l.46 [TYPO]: "the the" -> "then the" > > Chapter 6: > p.231,l.47 [SUGG]: remove "tremendous" > p.232,l.17 [SUGG]: remove PARMACS rationale, seems obsolete nowadays > p.233,l.19 [SUGG]: remove EXPRESS/PARMACS rationale > > Chapter 7: > p.249,l.5 [SUGG]: "for C" -> "for C and C++" > p.261-262 [SUGG]: move MPI-2 errir classes into running discussion/tables > > Chapter 8: [SUGG] Rename chapter to > "Controlling the functionality: The info object" > or something like this. Any better/good suggestions? > p.271,l.14 [SUGG]: Remove this line > p.274,l.36 [TYPO]: change font in (key,value) to sf. Also elsewhere > p.275,l.5 [TYPO]: font > p.276,l.37 [TYPO]: font should be $n$th > > Chapter 9: > p.279,l.21ff [TYPO]: Remove/reformulate this historical/anecdotical remark > > Chapter 10: > p.312,l.15 [COMM]: Note that here it is said that counts are "(nonnegative > integers)"; same should be done also for p2p and collectives, also for > consistency reasons. > p.313,l.29,l.32 [QUESTION]: is it "high quality" or "high-quality"? > p.315,l.11 [TYPO]: MPI_TYPE_EXTENT -> MPI_TYPE_GET_EXTENT (also in next > examples) > p.330,l.10 [QUESTION]: what is the state of Fortran compilers at this time > of writing? > > Chapter 11: > > Chapter 12: > p.432,l.27 [SUGG]: > Make reference to subarray constructor definition, 3.12.4, p.86 > > Chapter 13: > p.435,l.24 [SUGG]: modify, only "MPI" > p.436,l.13 [SUGG]: "as of writing" - this state of affairs has changed > > Chapter 14: > p.482,l.27 [SUGG]: Section 14.6 can be dropped? > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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) From rabenseifner at [hidden] Wed Apr 2 11:25:45 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Wed, 02 Apr 2008 18:25:45 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan Message-ID: Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, Rajeev, Jeff, and Alexander, you are responsible for one ore more chapters of MPI-2.1 until the meeting. It is a tough schedule: ----------------------- * Tues, April 1, my ROUND ONE is finished and the write token is logically passed to all chapter authors: - You have read access to the source (via SVN) and the pdf. - You have write access to your local SVN copy. - You will get write access to the SVN in a few days. * Fri., April 11, chapter authors have finished ROUND TWO. - This is a hard deadline (because I've to go on travel) * Sat., April 12, I will produce mpi-report.pdf as basis for review (I cannot do later, because April 14-17, I'm on travel) * Mon.-Thu., April 14-17, strong review by the reviewer group * Fri., April 18, reviews - if necessary must be included - by the chapter authors * Sat., April 19, I will produce final mpi-report.pdf which is basis for - final reviews through the reviewer group - official reading at the April 28-30, 2008 meeting. (I cannot do later because I'm on travel April 20-26) The goals of your work as chapter author: ----------------------------------------- - Remove references to MPI-1 and MPI-2. - Substitute by MPI. - Necessary modifications to achieve this goal. With this, we should have a single MPI-2.1 standard that does not "know" the MPI-1 or MPI-2 history of individual functions. ** This should be mainly a task in the area of chapter-introductions. ** Please, never change the wording of function definitions. Exceptions: - There are routines that are deprecated and that are already referenced in a consistent way. My recommendation: Current wording: There are *new* function, and existing are now deprecated. Proposal: There are functions, and there exist also deprecated functions with (nearly) same functionality but deprecated due to some lack in the bindings (or functionality) - There is history information in the frontmatter. - there is a change-log annex with limited memory (only previous version) Technical editing rule: ----------------------- You must identify all of your changes: a) new/modified wording - you are highlighting your new/modified wording with: \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification .... your modified / new wording .... \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification b) Moved paragraphs, sentences, ... - you are highlighting the first word of the moved text with: \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move First-word \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move ... rest of the moved text.... % MPI-2.1 round-two - end of text-move Caution: These macros work only in black parts of the text. In blue parts you must substitute \mpiiidotiMergeNEWforSINGLEendI% by \mpiiidotiMergeNEWforSINGLEendII% The highlighting is done with red color. (There are only a few other sentences from me magenta. Therefore red should be the best to highlight the round-two modifications.) Rsponsibilities: ---------------- * Frontmatter mpi-report.tex Bill Gropp * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) * 1. Introduction intro.tex Bill Gropp - 2. Terms terms-2.tex Tony Skjellum * 3. Point-to-point pt2pt.tex Rich Graham * 4. Collectives coll.tex Adam Moody * 5. Groups, etc. context.tex Dick Treumann - 6. Toplogies topol.tex Jesper Traeff * 7. Environment inquiry.tex George Bosilca - 8. Miscellany misc-2.tex Jesper Traeff - 9. Process Crea... dynamic-2.tex David Solt - 10. One-sided Comm one-sided-2.tex Jepser Traeff - 11. External Int. ei-2.tex Bronis de Supinski - 12. IO io-2.tex Rajeev Thakur - 13. Lang.Binding binding-2.tex Jeff Squyres - 14. Profiling prof.tex Bronis de Supinski - 15. Deprecated deprecated.tex Rolf Rabenseifner - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov - Annex B Change-log changes.tex Rolf Rabenseifner - Bibliography refs.bib Bill Gropp - Index MAKE-FUNC-INDEX Rolf Rabenseifner Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, only small work expected * There was a significant merge, or new text, or ..., more work expected I wish you a good start and good luck with your chapter. 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) From bronis at [hidden] Wed Apr 2 15:03:07 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Wed, 2 Apr 2008 13:03:07 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: Rolf: I have finished editing chapter 14: Profiling. I have attached the modified prof.tex since I do not yet have write access. More importantly, either there is a problem with the 2.1 macros or I am doing something wrong (I think it is the first but I am not LaTex fluent enough to be certain). Specifically, the first letter of the word following the end markers does not appear in the generated PDF. I would appreciate it if you could look into which it is. Another observation is that the macro does not work around empty sections. In particular, I tried to mark the section that I moved with the macros, with the original text commented out. I tried to do the same for some MPI-1.0 text that was contradictory to or redundant with the text that I moved. Having those empty macro regions caused the compile to fail. It might be nice to have some way to flag the deleted text, with the convention, at least for now, of just commenting it out and not to delete it entirely from the file. Let me know if I am doing things right here and then I will move on to fixing chapter 11: External Interfaces. Thanks, Bronis On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > Rajeev, Jeff, and Alexander, > > you are responsible for one ore more chapters of MPI-2.1 until the > meeting. > > It is a tough schedule: > ----------------------- > > * Tues, April 1, my ROUND ONE is finished and the write token is > logically passed to all chapter authors: > - You have read access to the source (via SVN) and the pdf. > - You have write access to your local SVN copy. > - You will get write access to the SVN in a few days. > * Fri., April 11, chapter authors have finished ROUND TWO. > - This is a hard deadline (because I've to go on travel) > * Sat., April 12, I will produce mpi-report.pdf as basis for review > (I cannot do later, because April 14-17, I'm on travel) > * Mon.-Thu., April 14-17, strong review by the reviewer group > * Fri., April 18, reviews - if necessary must be included - > by the chapter authors > * Sat., April 19, I will produce final mpi-report.pdf > which is basis for > - final reviews through the reviewer group > - official reading at the April 28-30, 2008 meeting. > (I cannot do later because I'm on travel April 20-26) > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > Rsponsibilities: > ---------------- > > * Frontmatter mpi-report.tex Bill Gropp > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > * 1. Introduction intro.tex Bill Gropp > - 2. Terms terms-2.tex Tony Skjellum > * 3. Point-to-point pt2pt.tex Rich Graham > * 4. Collectives coll.tex Adam Moody > * 5. Groups, etc. context.tex Dick Treumann > - 6. Toplogies topol.tex Jesper Traeff > * 7. Environment inquiry.tex George Bosilca > - 8. Miscellany misc-2.tex Jesper Traeff > - 9. Process Crea... dynamic-2.tex David Solt > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > - 11. External Int. ei-2.tex Bronis de Supinski > - 12. IO io-2.tex Rajeev Thakur > - 13. Lang.Binding binding-2.tex Jeff Squyres > - 14. Profiling prof.tex Bronis de Supinski > - 15. Deprecated deprecated.tex Rolf Rabenseifner > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > - Annex B Change-log changes.tex Rolf Rabenseifner > - Bibliography refs.bib Bill Gropp > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > only small work expected > * There was a significant merge, or new text, or ..., > more work expected > > I wish you a good start and good luck with your chapter. > > 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) > * -------------- next part -------------- A non-text attachment was scrubbed... Name: prof.tex Type: application/x-tex Size: 19214 bytes Desc: prof.tex URL: From bronis at [hidden] Wed Apr 2 16:14:56 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Wed, 2 Apr 2008 14:14:56 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: Rolf: I have not gone through Chapter 11 thoroughly yet but I have already noticed some major changes that I would suggest. First Section 11.6: "Decoding a Datatype" seems out of place in the merged document. It would make sense to me to have all of the datatype functions together. If we don't make datatypes a separate chapter, then this section (11.6) should be moved into chapter 3, near section 3.12: "Derived Datatypes". Ideally, it would be merged into that section since it is clearly part of that functionality. Second, Section 11.5: "Error Classes, Error Codes, and Error Handlers" is strongly related to Section 7.3: "Error Handling", and Section 7.4: "Error Codes and Classes". Clearly, these sections should be merged. In fact, this overlap makes me ask why have we not merged Chapters 7 and 11? What is the difference between "Environmental Management" and "External Interfaces"? I think this question needs to be resolved before I go further on working on Chapter 11. Perhaps George and I should coordinate merging these chapters after I coordinate moving the datatype decoding functionality into chapter 3 with Rich... Bronis On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > Rolf: > > I have finished editing chapter 14: Profiling. I have > attached the modified prof.tex since I do not yet have > write access. More importantly, either there is a problem > with the 2.1 macros or I am doing something wrong (I think > it is the first but I am not LaTex fluent enough to be > certain). Specifically, the first letter of the word > following the end markers does not appear in the generated > PDF. I would appreciate it if you could look into which it is. > > Another observation is that the macro does not work around > empty sections. In particular, I tried to mark the section > that I moved with the macros, with the original text commented > out. I tried to do the same for some MPI-1.0 text that was > contradictory to or redundant with the text that I moved. > Having those empty macro regions caused the compile to fail. > It might be nice to have some way to flag the deleted text, > with the convention, at least for now, of just commenting > it out and not to delete it entirely from the file. > > Let me know if I am doing things right here and then I will > move on to fixing chapter 11: External Interfaces. Thanks, > > Bronis > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > Rajeev, Jeff, and Alexander, > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > meeting. > > > > It is a tough schedule: > > ----------------------- > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > logically passed to all chapter authors: > > - You have read access to the source (via SVN) and the pdf. > > - You have write access to your local SVN copy. > > - You will get write access to the SVN in a few days. > > * Fri., April 11, chapter authors have finished ROUND TWO. > > - This is a hard deadline (because I've to go on travel) > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > (I cannot do later, because April 14-17, I'm on travel) > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > * Fri., April 18, reviews - if necessary must be included - > > by the chapter authors > > * Sat., April 19, I will produce final mpi-report.pdf > > which is basis for > > - final reviews through the reviewer group > > - official reading at the April 28-30, 2008 meeting. > > (I cannot do later because I'm on travel April 20-26) > > > > The goals of your work as chapter author: > > ----------------------------------------- > > > > - Remove references to MPI-1 and MPI-2. > > - Substitute by MPI. > > - Necessary modifications to achieve this goal. > > > > With this, we should have a single MPI-2.1 standard that does > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > ** This should be mainly a task in the area of chapter-introductions. > > ** Please, never change the wording of function definitions. > > > > Exceptions: > > - There are routines that are deprecated and that are > > already referenced in a consistent way. > > My recommendation: > > Current wording: > > There are *new* function, and existing are now deprecated. > > Proposal: > > There are functions, and there exist also deprecated functions > > with (nearly) same functionality but deprecated due to some lack > > in the bindings (or functionality) > > - There is history information in the frontmatter. > > - there is a change-log annex with limited memory (only previous version) > > > > Technical editing rule: > > ----------------------- > > > > You must identify all of your changes: > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > .... your modified / new wording .... > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > of the moved text with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > First-word > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > ... rest of the moved text.... > > % MPI-2.1 round-two - end of text-move > > > > Caution: These macros work only in black parts of the text. > > > > In blue parts you must substitute > > \mpiiidotiMergeNEWforSINGLEendI% > > by > > \mpiiidotiMergeNEWforSINGLEendII% > > > > The highlighting is done with red color. > > (There are only a few other sentences from me magenta. > > Therefore red should be the best to highlight the round-two modifications.) > > > > Rsponsibilities: > > ---------------- > > > > * Frontmatter mpi-report.tex Bill Gropp > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > * 1. Introduction intro.tex Bill Gropp > > - 2. Terms terms-2.tex Tony Skjellum > > * 3. Point-to-point pt2pt.tex Rich Graham > > * 4. Collectives coll.tex Adam Moody > > * 5. Groups, etc. context.tex Dick Treumann > > - 6. Toplogies topol.tex Jesper Traeff > > * 7. Environment inquiry.tex George Bosilca > > - 8. Miscellany misc-2.tex Jesper Traeff > > - 9. Process Crea... dynamic-2.tex David Solt > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > - 11. External Int. ei-2.tex Bronis de Supinski > > - 12. IO io-2.tex Rajeev Thakur > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > - 14. Profiling prof.tex Bronis de Supinski > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > - Annex B Change-log changes.tex Rolf Rabenseifner > > - Bibliography refs.bib Bill Gropp > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > only small work expected > > * There was a significant merge, or new text, or ..., > > more work expected > > > > I wish you a good start and good luck with your chapter. > > > > 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) > > From jsquyres at [hidden] Wed Apr 2 16:21:44 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Wed, 2 Apr 2008 17:21:44 -0400 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: I hate to throw up another red flag, but as I was paging through the doc, I was wondering if Chapter 13 (C++/F90) should go away, and have all that content merged elsewhere in the doc: - most would go to Terms and Conventions - some would go to Point-to-Point Communication (e.g., the stuff about Comm::Clone() and friends) - ...etc. I can make a specific proposal about this, but would want some feedback that people generally thought it was a good idea first. On Apr 2, 2008, at 5:14 PM, Bronis R. de Supinski wrote: > > > Rolf: > > I have not gone through Chapter 11 thoroughly yet but I have > already noticed some major changes that I would suggest. > > First Section 11.6: "Decoding a Datatype" seems out of place > in the merged document. It would make sense to me to have all > of the datatype functions together. If we don't make datatypes > a separate chapter, then this section (11.6) should be moved > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, > it would be merged into that section since it is clearly part > of that functionality. > > Second, Section 11.5: "Error Classes, Error Codes, and Error > Handlers" is strongly related to Section 7.3: "Error Handling", > and Section 7.4: "Error Codes and Classes". Clearly, these > sections should be merged. In fact, this overlap makes me ask > why have we not merged Chapters 7 and 11? What is the difference > between "Environmental Management" and "External Interfaces"? > > I think this question needs to be resolved before I go further > on working on Chapter 11. Perhaps George and I should coordinate > merging these chapters after I coordinate moving the datatype > decoding functionality into chapter 3 with Rich... > > Bronis > > > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > >> >> Rolf: >> >> I have finished editing chapter 14: Profiling. I have >> attached the modified prof.tex since I do not yet have >> write access. More importantly, either there is a problem >> with the 2.1 macros or I am doing something wrong (I think >> it is the first but I am not LaTex fluent enough to be >> certain). Specifically, the first letter of the word >> following the end markers does not appear in the generated >> PDF. I would appreciate it if you could look into which it is. >> >> Another observation is that the macro does not work around >> empty sections. In particular, I tried to mark the section >> that I moved with the macros, with the original text commented >> out. I tried to do the same for some MPI-1.0 text that was >> contradictory to or redundant with the text that I moved. >> Having those empty macro regions caused the compile to fail. >> It might be nice to have some way to flag the deleted text, >> with the convention, at least for now, of just commenting >> it out and not to delete it entirely from the file. >> >> Let me know if I am doing things right here and then I will >> move on to fixing chapter 11: External Interfaces. Thanks, >> >> Bronis >> >> >> On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: >> >>> Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, >>> Rajeev, Jeff, and Alexander, >>> >>> you are responsible for one ore more chapters of MPI-2.1 until the >>> meeting. >>> >>> It is a tough schedule: >>> ----------------------- >>> >>> * Tues, April 1, my ROUND ONE is finished and the write token is >>> logically passed to all chapter authors: >>> - You have read access to the source (via SVN) and the pdf. >>> - You have write access to your local SVN copy. >>> - You will get write access to the SVN in a few days. >>> * Fri., April 11, chapter authors have finished ROUND TWO. >>> - This is a hard deadline (because I've to go on travel) >>> * Sat., April 12, I will produce mpi-report.pdf as basis for review >>> (I cannot do later, because April 14-17, I'm on travel) >>> * Mon.-Thu., April 14-17, strong review by the reviewer group >>> * Fri., April 18, reviews - if necessary must be included - >>> by the chapter authors >>> * Sat., April 19, I will produce final mpi-report.pdf >>> which is basis for >>> - final reviews through the reviewer group >>> - official reading at the April 28-30, 2008 meeting. >>> (I cannot do later because I'm on travel April 20-26) >>> >>> The goals of your work as chapter author: >>> ----------------------------------------- >>> >>> - Remove references to MPI-1 and MPI-2. >>> - Substitute by MPI. >>> - Necessary modifications to achieve this goal. >>> >>> With this, we should have a single MPI-2.1 standard that does >>> not "know" the MPI-1 or MPI-2 history of individual functions. >>> >>> ** This should be mainly a task in the area of chapter- >>> introductions. >>> ** Please, never change the wording of function definitions. >>> >>> Exceptions: >>> - There are routines that are deprecated and that are >>> already referenced in a consistent way. >>> My recommendation: >>> Current wording: >>> There are *new* function, and existing are now deprecated. >>> Proposal: >>> There are functions, and there exist also deprecated functions >>> with (nearly) same functionality but deprecated due to some lack >>> in the bindings (or functionality) >>> - There is history information in the frontmatter. >>> - there is a change-log annex with limited memory (only previous >>> version) >>> >>> Technical editing rule: >>> ----------------------- >>> >>> You must identify all of your changes: >>> >>> a) new/modified wording - you are highlighting your new/modified >>> wording with: >>> >>> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >>> modification >>> .... your modified / new wording .... >>> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of >>> modification >>> >>> b) Moved paragraphs, sentences, ... - you are highlighting the >>> first word >>> of the moved text with: >>> >>> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >>> text-move >>> First-word >>> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text- >>> move >>> ... rest of the moved text.... >>> % MPI-2.1 round-two - end of text-move >>> >>> Caution: These macros work only in black parts of the text. >>> >>> In blue parts you must substitute >>> \mpiiidotiMergeNEWforSINGLEendI% >>> by >>> \mpiiidotiMergeNEWforSINGLEendII% >>> >>> The highlighting is done with red color. >>> (There are only a few other sentences from me magenta. >>> Therefore red should be the best to highlight the round-two >>> modifications.) >>> >>> Rsponsibilities: >>> ---------------- >>> >>> * Frontmatter mpi-report.tex Bill Gropp >>> * Acknowledgements credits.tex Rich Graham(text) + >>> Rolf(emails-auth.) >>> * 1. Introduction intro.tex Bill Gropp >>> - 2. Terms terms-2.tex Tony Skjellum >>> * 3. Point-to-point pt2pt.tex Rich Graham >>> * 4. Collectives coll.tex Adam Moody >>> * 5. Groups, etc. context.tex Dick Treumann >>> - 6. Toplogies topol.tex Jesper Traeff >>> * 7. Environment inquiry.tex George Bosilca >>> - 8. Miscellany misc-2.tex Jesper Traeff >>> - 9. Process Crea... dynamic-2.tex David Solt >>> - 10. One-sided Comm one-sided-2.tex Jepser Traeff >>> - 11. External Int. ei-2.tex Bronis de Supinski >>> - 12. IO io-2.tex Rajeev Thakur >>> - 13. Lang.Binding binding-2.tex Jeff Squyres >>> - 14. Profiling prof.tex Bronis de Supinski >>> - 15. Deprecated deprecated.tex Rolf Rabenseifner >>> - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov >>> - Annex B Change-log changes.tex Rolf Rabenseifner >>> - Bibliography refs.bib Bill Gropp >>> - Index MAKE-FUNC-INDEX Rolf Rabenseifner >>> >>> Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, >>> only small work expected >>> * There was a significant merge, or new text, or ..., >>> more work expected >>> >>> I wish you a good start and good luck with your chapter. >>> >>> 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) >>> -- Jeff Squyres Cisco Systems From alexander.supalov at [hidden] Wed Apr 2 16:23:31 2008 From: alexander.supalov at [hidden] (Supalov, Alexander) Date: Wed, 2 Apr 2008 22:23:31 +0100 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <5ECAB1304A8B5B4CB3F9D6C01E4E21A201338F77@swsmsx413.ger.corp.intel.com> Hi, We may want to reduce the number of top level sections in the standard. In my opinion that I expressed to Rolf a couple of weeks ago, quite a few sections, like the ones mentioned by Bronis, should rather belong to a big Miscellany chapter rather than figure up there by themselves. They may also be merged/reformed, too. However, this is going to be a bigger change than envisioned originally. I wonder whether we should decide right away whether we can afford this now without slipping the planned MPI-2.1 delivery in September. A possible way would be to fix small things now and do second pass of major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. Best regards. Alexander -----Original Message----- From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] Sent: Wednesday, April 02, 2008 11:15 PM To: Rolf Rabenseifner Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan Rolf: I have not gone through Chapter 11 thoroughly yet but I have already noticed some major changes that I would suggest. First Section 11.6: "Decoding a Datatype" seems out of place in the merged document. It would make sense to me to have all of the datatype functions together. If we don't make datatypes a separate chapter, then this section (11.6) should be moved into chapter 3, near section 3.12: "Derived Datatypes". Ideally, it would be merged into that section since it is clearly part of that functionality. Second, Section 11.5: "Error Classes, Error Codes, and Error Handlers" is strongly related to Section 7.3: "Error Handling", and Section 7.4: "Error Codes and Classes". Clearly, these sections should be merged. In fact, this overlap makes me ask why have we not merged Chapters 7 and 11? What is the difference between "Environmental Management" and "External Interfaces"? I think this question needs to be resolved before I go further on working on Chapter 11. Perhaps George and I should coordinate merging these chapters after I coordinate moving the datatype decoding functionality into chapter 3 with Rich... Bronis On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > Rolf: > > I have finished editing chapter 14: Profiling. I have > attached the modified prof.tex since I do not yet have > write access. More importantly, either there is a problem > with the 2.1 macros or I am doing something wrong (I think > it is the first but I am not LaTex fluent enough to be > certain). Specifically, the first letter of the word > following the end markers does not appear in the generated > PDF. I would appreciate it if you could look into which it is. > > Another observation is that the macro does not work around > empty sections. In particular, I tried to mark the section > that I moved with the macros, with the original text commented > out. I tried to do the same for some MPI-1.0 text that was > contradictory to or redundant with the text that I moved. > Having those empty macro regions caused the compile to fail. > It might be nice to have some way to flag the deleted text, > with the convention, at least for now, of just commenting > it out and not to delete it entirely from the file. > > Let me know if I am doing things right here and then I will > move on to fixing chapter 11: External Interfaces. Thanks, > > Bronis > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > Rajeev, Jeff, and Alexander, > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > meeting. > > > > It is a tough schedule: > > ----------------------- > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > logically passed to all chapter authors: > > - You have read access to the source (via SVN) and the pdf. > > - You have write access to your local SVN copy. > > - You will get write access to the SVN in a few days. > > * Fri., April 11, chapter authors have finished ROUND TWO. > > - This is a hard deadline (because I've to go on travel) > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > (I cannot do later, because April 14-17, I'm on travel) > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > * Fri., April 18, reviews - if necessary must be included - > > by the chapter authors > > * Sat., April 19, I will produce final mpi-report.pdf > > which is basis for > > - final reviews through the reviewer group > > - official reading at the April 28-30, 2008 meeting. > > (I cannot do later because I'm on travel April 20-26) > > > > The goals of your work as chapter author: > > ----------------------------------------- > > > > - Remove references to MPI-1 and MPI-2. > > - Substitute by MPI. > > - Necessary modifications to achieve this goal. > > > > With this, we should have a single MPI-2.1 standard that does > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > ** This should be mainly a task in the area of chapter-introductions. > > ** Please, never change the wording of function definitions. > > > > Exceptions: > > - There are routines that are deprecated and that are > > already referenced in a consistent way. > > My recommendation: > > Current wording: > > There are *new* function, and existing are now deprecated. > > Proposal: > > There are functions, and there exist also deprecated functions > > with (nearly) same functionality but deprecated due to some lack > > in the bindings (or functionality) > > - There is history information in the frontmatter. > > - there is a change-log annex with limited memory (only previous version) > > > > Technical editing rule: > > ----------------------- > > > > You must identify all of your changes: > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > .... your modified / new wording .... > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > of the moved text with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > First-word > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > ... rest of the moved text.... > > % MPI-2.1 round-two - end of text-move > > > > Caution: These macros work only in black parts of the text. > > > > In blue parts you must substitute > > \mpiiidotiMergeNEWforSINGLEendI% > > by > > \mpiiidotiMergeNEWforSINGLEendII% > > > > The highlighting is done with red color. > > (There are only a few other sentences from me magenta. > > Therefore red should be the best to highlight the round-two modifications.) > > > > Rsponsibilities: > > ---------------- > > > > * Frontmatter mpi-report.tex Bill Gropp > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > * 1. Introduction intro.tex Bill Gropp > > - 2. Terms terms-2.tex Tony Skjellum > > * 3. Point-to-point pt2pt.tex Rich Graham > > * 4. Collectives coll.tex Adam Moody > > * 5. Groups, etc. context.tex Dick Treumann > > - 6. Toplogies topol.tex Jesper Traeff > > * 7. Environment inquiry.tex George Bosilca > > - 8. Miscellany misc-2.tex Jesper Traeff > > - 9. Process Crea... dynamic-2.tex David Solt > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > - 11. External Int. ei-2.tex Bronis de Supinski > > - 12. IO io-2.tex Rajeev Thakur > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > - 14. Profiling prof.tex Bronis de Supinski > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > - Annex B Change-log changes.tex Rolf Rabenseifner > > - Bibliography refs.bib Bill Gropp > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > only small work expected > > * There was a significant merge, or new text, or ..., > > more work expected > > > > I wish you a good start and good luck with your chapter. > > > > 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) > > --------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen Germany Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr. VAT Registration No.: DE129385895 Citibank Frankfurt (BLZ 502 109 00) 600119052 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From bronis at [hidden] Wed Apr 2 16:26:13 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Wed, 2 Apr 2008 14:26:13 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <5ECAB1304A8B5B4CB3F9D6C01E4E21A201338F77@swsmsx413.ger.corp.intel.com> Message-ID: All: I thoroughly agree with the sentiment that many expressed that we are better off slipping the release of 2.1 two or four months more in order to get it right than hurrying to get it out the door. It is likely to be THE standard for a fairly long time and having it broken to begin with does not seem wise. Bronis On Wed, 2 Apr 2008, Supalov, Alexander wrote: > Hi, > > We may want to reduce the number of top level sections in the standard. > In my opinion that I expressed to Rolf a couple of weeks ago, quite a > few sections, like the ones mentioned by Bronis, should rather belong to > a big Miscellany chapter rather than figure up there by themselves. They > may also be merged/reformed, too. > > However, this is going to be a bigger change than envisioned originally. > I wonder whether we should decide right away whether we can afford this > now without slipping the planned MPI-2.1 delivery in September. A > possible way would be to fix small things now and do second pass of > major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. > > Best regards. > > Alexander > > -----Original Message----- > From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] > Sent: Wednesday, April 02, 2008 11:15 PM > To: Rolf Rabenseifner > Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard > Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev > Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan > > > > Rolf: > > I have not gone through Chapter 11 thoroughly yet but I have > already noticed some major changes that I would suggest. > > First Section 11.6: "Decoding a Datatype" seems out of place > in the merged document. It would make sense to me to have all > of the datatype functions together. If we don't make datatypes > a separate chapter, then this section (11.6) should be moved > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, > it would be merged into that section since it is clearly part > of that functionality. > > Second, Section 11.5: "Error Classes, Error Codes, and Error > Handlers" is strongly related to Section 7.3: "Error Handling", > and Section 7.4: "Error Codes and Classes". Clearly, these > sections should be merged. In fact, this overlap makes me ask > why have we not merged Chapters 7 and 11? What is the difference > between "Environmental Management" and "External Interfaces"? > > I think this question needs to be resolved before I go further > on working on Chapter 11. Perhaps George and I should coordinate > merging these chapters after I coordinate moving the datatype > decoding functionality into chapter 3 with Rich... > > Bronis > > > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > > > > Rolf: > > > > I have finished editing chapter 14: Profiling. I have > > attached the modified prof.tex since I do not yet have > > write access. More importantly, either there is a problem > > with the 2.1 macros or I am doing something wrong (I think > > it is the first but I am not LaTex fluent enough to be > > certain). Specifically, the first letter of the word > > following the end markers does not appear in the generated > > PDF. I would appreciate it if you could look into which it is. > > > > Another observation is that the macro does not work around > > empty sections. In particular, I tried to mark the section > > that I moved with the macros, with the original text commented > > out. I tried to do the same for some MPI-1.0 text that was > > contradictory to or redundant with the text that I moved. > > Having those empty macro regions caused the compile to fail. > > It might be nice to have some way to flag the deleted text, > > with the convention, at least for now, of just commenting > > it out and not to delete it entirely from the file. > > > > Let me know if I am doing things right here and then I will > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > Bronis > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > > Rajeev, Jeff, and Alexander, > > > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > > meeting. > > > > > > It is a tough schedule: > > > ----------------------- > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > > logically passed to all chapter authors: > > > - You have read access to the source (via SVN) and the > pdf. > > > - You have write access to your local SVN copy. > > > - You will get write access to the SVN in a few days. > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > - This is a hard deadline (because I've to go on travel) > > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > > (I cannot do later, because April 14-17, I'm on travel) > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > * Fri., April 18, reviews - if necessary must be included - > > > by the chapter authors > > > * Sat., April 19, I will produce final mpi-report.pdf > > > which is basis for > > > - final reviews through the reviewer group > > > - official reading at the April 28-30, 2008 meeting. > > > (I cannot do later because I'm on travel April 20-26) > > > > > > The goals of your work as chapter author: > > > ----------------------------------------- > > > > > > - Remove references to MPI-1 and MPI-2. > > > - Substitute by MPI. > > > - Necessary modifications to achieve this goal. > > > > > > With this, we should have a single MPI-2.1 standard that does > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > ** This should be mainly a task in the area of > chapter-introductions. > > > ** Please, never change the wording of function definitions. > > > > > > Exceptions: > > > - There are routines that are deprecated and that are > > > already referenced in a consistent way. > > > My recommendation: > > > Current wording: > > > There are *new* function, and existing are now deprecated. > > > Proposal: > > > There are functions, and there exist also deprecated functions > > > with (nearly) same functionality but deprecated due to some > lack > > > in the bindings (or functionality) > > > - There is history information in the frontmatter. > > > - there is a change-log annex with limited memory (only previous > version) > > > > > > Technical editing rule: > > > ----------------------- > > > > > > You must identify all of your changes: > > > > > > a) new/modified wording - you are highlighting your new/modified > wording with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > modification > > > .... your modified / new wording .... > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of > modification > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first > word > > > of the moved text with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > text-move > > > First-word > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing > text-move > > > ... rest of the moved text.... > > > % MPI-2.1 round-two - end of text-move > > > > > > Caution: These macros work only in black parts of the text. > > > > > > In blue parts you must substitute > > > \mpiiidotiMergeNEWforSINGLEendI% > > > by > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > The highlighting is done with red color. > > > (There are only a few other sentences from me magenta. > > > Therefore red should be the best to highlight the round-two > modifications.) > > > > > > Rsponsibilities: > > > ---------------- > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > * Acknowledgements credits.tex Rich Graham(text) + > Rolf(emails-auth.) > > > * 1. Introduction intro.tex Bill Gropp > > > - 2. Terms terms-2.tex Tony Skjellum > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > * 4. Collectives coll.tex Adam Moody > > > * 5. Groups, etc. context.tex Dick Treumann > > > - 6. Toplogies topol.tex Jesper Traeff > > > * 7. Environment inquiry.tex George Bosilca > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > - 9. Process Crea... dynamic-2.tex David Solt > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > - 12. IO io-2.tex Rajeev Thakur > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > - 14. Profiling prof.tex Bronis de Supinski > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > - Bibliography refs.bib Bill Gropp > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > only small work expected > > > * There was a significant merge, or new text, or ..., > > > more work expected > > > > > > I wish you a good start and good luck with your chapter. > > > > > > 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) > > > > --------------------------------------------------------------------- > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen Germany > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > VAT Registration No.: DE129385895 > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > From rabenseifner at [hidden] Thu Apr 3 02:44:55 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 03 Apr 2008 09:44:55 +0200 Subject: [Mpi-21] Fwd: TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: On Wed, 02 Apr 2008 18:25:45 +0200 "Rolf Rabenseifner" wrote: > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > Rajeev, Jeff, and Alexander, > > you are responsible for one ore more chapters of MPI-2.1 until the > meeting. > > It is a tough schedule: > ----------------------- > > * Tues, April 1, my ROUND ONE is finished and the write token is > logically passed to all chapter authors: > - You have read access to the source (via SVN) and the pdf. > - You have write access to your local SVN copy. > - You will get write access to the SVN in a few days. > * Fri., April 11, chapter authors have finished ROUND TWO. > - This is a hard deadline (because I've to go on travel) > * Sat., April 12, I will produce mpi-report.pdf as basis for review > (I cannot do later, because April 14-17, I'm on travel) > * Mon.-Thu., April 14-17, strong review by the reviewer group > * Fri., April 18, reviews - if necessary must be included - > by the chapter authors > * Sat., April 19, I will produce final mpi-report.pdf > which is basis for > - final reviews through the reviewer group > - official reading at the April 28-30, 2008 meeting. > (I cannot do later because I'm on travel April 20-26) > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > Rsponsibilities: > ---------------- > > * Frontmatter mpi-report.tex Bill Gropp > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > * 1. Introduction intro.tex Bill Gropp > - 2. Terms terms-2.tex Tony Skjellum > * 3. Point-to-point pt2pt.tex Rich Graham > * 4. Collectives coll.tex Adam Moody > * 5. Groups, etc. context.tex Dick Treumann > - 6. Toplogies topol.tex Jesper Traeff > * 7. Environment inquiry.tex George Bosilca > - 8. Miscellany misc-2.tex Jesper Traeff > - 9. Process Crea... dynamic-2.tex David Solt > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > - 11. External Int. ei-2.tex Bronis de Supinski > - 12. IO io-2.tex Rajeev Thakur > - 13. Lang.Binding binding-2.tex Jeff Squyres > - 14. Profiling prof.tex Bronis de Supinski > - 15. Deprecated deprecated.tex Rolf Rabenseifner > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > - Annex B Change-log changes.tex Rolf Rabenseifner > - Bibliography refs.bib Bill Gropp > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > only small work expected > * There was a significant merge, or new text, or ..., > more work expected > > I wish you a good start and good luck with your chapter. > > 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) From rabenseifner at [hidden] Thu Apr 3 06:01:57 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 03 Apr 2008 13:01:57 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: >>> Instead of a long To: list plus CC to the mailing list, >>> I recommend to send further discussion only to >>> "MPI 2.1 Mailing List" Hi all authors, please go into MPI-2.1 and call svn update You will mainly receive new mpi-macs.tex The error should be solved. If there is still a problem with empty sections, then coloring is of course invisible and therefore (only with empty sections) you may comment these special lines out, i.e. a %-sign before the \mpiiidotiMergeNEWforSINGLEbegin and endI or endII macros. My apologies about the inconvinience with this bug. I also svn commit'ed the new version of prof.tex from Bronis. Best regards Rolf On Wed, 2 Apr 2008 13:03:07 -0700 (PDT) "Bronis R. de Supinski" wrote: > > Rolf: > > I have finished editing chapter 14: Profiling. I have > attached the modified prof.tex since I do not yet have > write access. More importantly, either there is a problem > with the 2.1 macros or I am doing something wrong (I think > it is the first but I am not LaTex fluent enough to be > certain). Specifically, the first letter of the word > following the end markers does not appear in the generated > PDF. I would appreciate it if you could look into which it is. > > Another observation is that the macro does not work around > empty sections. In particular, I tried to mark the section > that I moved with the macros, with the original text commented > out. I tried to do the same for some MPI-1.0 text that was > contradictory to or redundant with the text that I moved. > Having those empty macro regions caused the compile to fail. > It might be nice to have some way to flag the deleted text, > with the convention, at least for now, of just commenting > it out and not to delete it entirely from the file. > > Let me know if I am doing things right here and then I will > move on to fixing chapter 11: External Interfaces. Thanks, > > Bronis > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > Rajeev, Jeff, and Alexander, > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > meeting. > > > > It is a tough schedule: > > ----------------------- > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > logically passed to all chapter authors: > > - You have read access to the source (via SVN) and the pdf. > > - You have write access to your local SVN copy. > > - You will get write access to the SVN in a few days. > > * Fri., April 11, chapter authors have finished ROUND TWO. > > - This is a hard deadline (because I've to go on travel) > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > (I cannot do later, because April 14-17, I'm on travel) > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > * Fri., April 18, reviews - if necessary must be included - > > by the chapter authors > > * Sat., April 19, I will produce final mpi-report.pdf > > which is basis for > > - final reviews through the reviewer group > > - official reading at the April 28-30, 2008 meeting. > > (I cannot do later because I'm on travel April 20-26) > > > > The goals of your work as chapter author: > > ----------------------------------------- > > > > - Remove references to MPI-1 and MPI-2. > > - Substitute by MPI. > > - Necessary modifications to achieve this goal. > > > > With this, we should have a single MPI-2.1 standard that does > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > ** This should be mainly a task in the area of chapter-introductions. > > ** Please, never change the wording of function definitions. > > > > Exceptions: > > - There are routines that are deprecated and that are > > already referenced in a consistent way. > > My recommendation: > > Current wording: > > There are *new* function, and existing are now deprecated. > > Proposal: > > There are functions, and there exist also deprecated functions > > with (nearly) same functionality but deprecated due to some lack > > in the bindings (or functionality) > > - There is history information in the frontmatter. > > - there is a change-log annex with limited memory (only previous version) > > > > Technical editing rule: > > ----------------------- > > > > You must identify all of your changes: > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > .... your modified / new wording .... > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > of the moved text with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > First-word > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > ... rest of the moved text.... > > % MPI-2.1 round-two - end of text-move > > > > Caution: These macros work only in black parts of the text. > > > > In blue parts you must substitute > > \mpiiidotiMergeNEWforSINGLEendI% > > by > > \mpiiidotiMergeNEWforSINGLEendII% > > > > The highlighting is done with red color. > > (There are only a few other sentences from me magenta. > > Therefore red should be the best to highlight the round-two modifications.) > > > > Rsponsibilities: > > ---------------- > > > > * Frontmatter mpi-report.tex Bill Gropp > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > * 1. Introduction intro.tex Bill Gropp > > - 2. Terms terms-2.tex Tony Skjellum > > * 3. Point-to-point pt2pt.tex Rich Graham > > * 4. Collectives coll.tex Adam Moody > > * 5. Groups, etc. context.tex Dick Treumann > > - 6. Toplogies topol.tex Jesper Traeff > > * 7. Environment inquiry.tex George Bosilca > > - 8. Miscellany misc-2.tex Jesper Traeff > > - 9. Process Crea... dynamic-2.tex David Solt > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > - 11. External Int. ei-2.tex Bronis de Supinski > > - 12. IO io-2.tex Rajeev Thakur > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > - 14. Profiling prof.tex Bronis de Supinski > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > - Annex B Change-log changes.tex Rolf Rabenseifner > > - Bibliography refs.bib Bill Gropp > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > only small work expected > > * There was a significant merge, or new text, or ..., > > more work expected > > > > I wish you a good start and good luck with your chapter. > > > > 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) > > 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) From rabenseifner at [hidden] Thu Apr 3 06:13:43 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 03 Apr 2008 13:13:43 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - delete text In-Reply-To: Message-ID: My recommendation for really deleted text, i.e., not only moved to another location: \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor Last word of the previous text \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line % the text you delete must be preceded with "% " % deprecated text % ... % deprecated text % MPI-2.1 round-two - end of deteted text Additionally, you shoud add this outcommented text to the end of removed_source.tex Best regards Rolf On Wed, 2 Apr 2008 13:03:07 -0700 (PDT) "Bronis R. de Supinski" wrote: > It might be nice to have some way to flag the deleted text, > with the convention, at least for now, of just commenting > it out and not to delete it entirely from the file. > > Let me know if I am doing things right here and then I will > move on to fixing chapter 11: External Interfaces. Thanks, > > Bronis > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > Rajeev, Jeff, and Alexander, > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > meeting. > > > > It is a tough schedule: > > ----------------------- > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > logically passed to all chapter authors: > > - You have read access to the source (via SVN) and the pdf. > > - You have write access to your local SVN copy. > > - You will get write access to the SVN in a few days. > > * Fri., April 11, chapter authors have finished ROUND TWO. > > - This is a hard deadline (because I've to go on travel) > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > (I cannot do later, because April 14-17, I'm on travel) > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > * Fri., April 18, reviews - if necessary must be included - > > by the chapter authors > > * Sat., April 19, I will produce final mpi-report.pdf > > which is basis for > > - final reviews through the reviewer group > > - official reading at the April 28-30, 2008 meeting. > > (I cannot do later because I'm on travel April 20-26) > > > > The goals of your work as chapter author: > > ----------------------------------------- > > > > - Remove references to MPI-1 and MPI-2. > > - Substitute by MPI. > > - Necessary modifications to achieve this goal. > > > > With this, we should have a single MPI-2.1 standard that does > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > ** This should be mainly a task in the area of chapter-introductions. > > ** Please, never change the wording of function definitions. > > > > Exceptions: > > - There are routines that are deprecated and that are > > already referenced in a consistent way. > > My recommendation: > > Current wording: > > There are *new* function, and existing are now deprecated. > > Proposal: > > There are functions, and there exist also deprecated functions > > with (nearly) same functionality but deprecated due to some lack > > in the bindings (or functionality) > > - There is history information in the frontmatter. > > - there is a change-log annex with limited memory (only previous version) > > > > Technical editing rule: > > ----------------------- > > > > You must identify all of your changes: > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > .... your modified / new wording .... > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > of the moved text with: > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > First-word > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > ... rest of the moved text.... > > % MPI-2.1 round-two - end of text-move > > > > Caution: These macros work only in black parts of the text. > > > > In blue parts you must substitute > > \mpiiidotiMergeNEWforSINGLEendI% > > by > > \mpiiidotiMergeNEWforSINGLEendII% > > > > The highlighting is done with red color. > > (There are only a few other sentences from me magenta. > > Therefore red should be the best to highlight the round-two modifications.) > > > > Rsponsibilities: > > ---------------- > > > > * Frontmatter mpi-report.tex Bill Gropp > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > * 1. Introduction intro.tex Bill Gropp > > - 2. Terms terms-2.tex Tony Skjellum > > * 3. Point-to-point pt2pt.tex Rich Graham > > * 4. Collectives coll.tex Adam Moody > > * 5. Groups, etc. context.tex Dick Treumann > > - 6. Toplogies topol.tex Jesper Traeff > > * 7. Environment inquiry.tex George Bosilca > > - 8. Miscellany misc-2.tex Jesper Traeff > > - 9. Process Crea... dynamic-2.tex David Solt > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > - 11. External Int. ei-2.tex Bronis de Supinski > > - 12. IO io-2.tex Rajeev Thakur > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > - 14. Profiling prof.tex Bronis de Supinski > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > - Annex B Change-log changes.tex Rolf Rabenseifner > > - Bibliography refs.bib Bill Gropp > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > only small work expected > > * There was a significant merge, or new text, or ..., > > more work expected > > > > I wish you a good start and good luck with your chapter. > > > > 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) > > 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) From rabenseifner at [hidden] Thu Apr 3 07:09:20 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 03 Apr 2008 14:09:20 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <5ECAB1304A8B5B4CB3F9D6C01E4E21A2013390BC@swsmsx413.ger.corp.intel.com> Message-ID: Hi all, yes, we need a decision as soon as possible. But first, it may be necessary to remove a wrong argument: - The standard will have 6 month lifetime, not more! - MPI 2.1 has to major goals: - make Ballots 1-4 as part of the official standard, - reduce the number of documents to one. All rest is nice to have - not a major goal. Until next Friday, only secure changes to intoductional text parts should be done. More must be moved to MPI-2.2. To have a monolithic MPI standard document can be added to the agenda of MPI-2.2. Here the official Scope of Effort as defined in January (see protocol): Scope of Effort: - Clarification to the MPI standards document, - resulting in a single document describing the full MPI 2.1 standard. - This includes merging of documents, text corrections, and added clarifying text. All these three goals are achieved! Current task is only to clean up small things, mainly (March protocol): Additional text-merge round with dedicated chapter authors. Goal: - Remove references to MPI-1 and MPI-2. - Substitute by MPI. - Necessary modifications to achieve this goal. MPI-2.2 can do it better in 6 month. The MPI-2.2 for this can start about 3 weeks after April meeting. I hope, you all can live with this decisions. (My work time is limited; this is another reason why I cannot accept a delay in the delivery of MPI-2.1) Bronis and George, my general statements do not answer you initial question: If you decide to move parts from Chap.11 to Chap.7, then you both mus discuss this. You both are responsible for these chapters. And you should first convince your reviewers: - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill - Chap.11: Bill and Rainer My recommendation: Express clearly which parts should be moved exactly to wich line (all based on page/line numbers as **printed** in Draft Apr. 1, 2008). Jeff, The idea of moving significant parts of Chap. 13 into Terms is absolutely against the spirit of how this document is written. The author tried to have only absolute necessary information before the fist MPI example on page 25 (In MPI-1, it was page 16). The MPI-2 Forum decided to put all the more detailed information into extra sections, and especially binding stuff at the end of the standard. I put the Profiling behind Binding (this may be a fault). C and Fortran have the clear advantage that all constants have the same name as the language-independently defined name, e.g. MPI_COMM_WORLD, MPI_INT, MPI_SUCCESS... . For MPI-2.1, I would keep it as it is. In MPI-2.2, there will be a longer discussion on C++ issues. Best regards Rolf On Thu, 3 Apr 2008 09:28:08 +0100 "Supalov, Alexander" wrote: > Hi, > > Whatever the decision will be, we need it now. We're close to the point > of no return for the September deadline. > > Best regards. > > Alexander > > -----Original Message----- > From: Jesper Larsson Traeff [mailto:traff_at_it.neclab.eu] > Sent: Thursday, April 03, 2008 9:26 AM > To: Bronis R. de Supinski > Cc: Supalov, Alexander; Rolf Rabenseifner; William Gropp; Tony Skjellum; > Rich Graham; Adam Moody; Richard Treumann; George Bosilca; David Solt; > Rajeev Thakur; Jeff Squyres; MPI 2.1 Mailing List > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan > > > Dear All, > > I agree with the comments of Bronis about datatypes - functionality > that belongs together should be together in the STANDARD! (which is what > we > are writing). To me it seems that this 2.1 is somewhat more than the > "merge" it was optimistically intended to be. Since this, as Bronis > says, will likely be THE STANDARD for years to come, and the entry point > for many new users, I think it is important that we get it right the > first time, and I believe this is possible (if not, we should abort the > attempt). It's good to have strict deadlines, but let's not be fanatical > > about that. I don't see any purpose whatsoever in putting out > intermediate > versions of 2.1 - as long as we are in limbo, 1.3 and 2.0 will work > perfectly, they have all the ballots included > > I will try to send comments on/updates of my chapters (these will, > I think/hope, not need so much) tomorrow/monday > > best regards > > Jesper > > On Wed, Apr 02, 2008 at 02:26:13PM -0700, Bronis R. de Supinski wrote: > > > > All: > > > > I thoroughly agree with the sentiment that many expressed > > that we are better off slipping the release of 2.1 two or > > four months more in order to get it right than hurrying to > > get it out the door. It is likely to be THE standard for > > a fairly long time and having it broken to begin with does > > not seem wise. > > > > Bronis > > > > > > On Wed, 2 Apr 2008, Supalov, Alexander wrote: > > > > > Hi, > > > > > > We may want to reduce the number of top level sections in the > standard. > > > In my opinion that I expressed to Rolf a couple of weeks ago, quite > a > > > few sections, like the ones mentioned by Bronis, should rather > belong to > > > a big Miscellany chapter rather than figure up there by themselves. > They > > > may also be merged/reformed, too. > > > > > > However, this is going to be a bigger change than envisioned > originally. > > > I wonder whether we should decide right away whether we can afford > this > > > now without slipping the planned MPI-2.1 delivery in September. A > > > possible way would be to fix small things now and do second pass of > > > major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. > > > > > > Best regards. > > > > > > Alexander > > > > > > -----Original Message----- > > > From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] > > > Sent: Wednesday, April 02, 2008 11:15 PM > > > To: Rolf Rabenseifner > > > Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard > > > Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev > > > Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List > > > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan > > > > > > > > > > > > Rolf: > > > > > > I have not gone through Chapter 11 thoroughly yet but I have > > > already noticed some major changes that I would suggest. > > > > > > First Section 11.6: "Decoding a Datatype" seems out of place > > > in the merged document. It would make sense to me to have all > > > of the datatype functions together. If we don't make datatypes > > > a separate chapter, then this section (11.6) should be moved > > > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, > > > it would be merged into that section since it is clearly part > > > of that functionality. > > > > > > Second, Section 11.5: "Error Classes, Error Codes, and Error > > > Handlers" is strongly related to Section 7.3: "Error Handling", > > > and Section 7.4: "Error Codes and Classes". Clearly, these > > > sections should be merged. In fact, this overlap makes me ask > > > why have we not merged Chapters 7 and 11? What is the difference > > > between "Environmental Management" and "External Interfaces"? > > > > > > I think this question needs to be resolved before I go further > > > on working on Chapter 11. Perhaps George and I should coordinate > > > merging these chapters after I coordinate moving the datatype > > > decoding functionality into chapter 3 with Rich... > > > > > > Bronis > > > > > > > > > > > > > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > > > > > > > > > > Rolf: > > > > > > > > I have finished editing chapter 14: Profiling. I have > > > > attached the modified prof.tex since I do not yet have > > > > write access. More importantly, either there is a problem > > > > with the 2.1 macros or I am doing something wrong (I think > > > > it is the first but I am not LaTex fluent enough to be > > > > certain). Specifically, the first letter of the word > > > > following the end markers does not appear in the generated > > > > PDF. I would appreciate it if you could look into which it is. > > > > > > > > Another observation is that the macro does not work around > > > > empty sections. In particular, I tried to mark the section > > > > that I moved with the macros, with the original text commented > > > > out. I tried to do the same for some MPI-1.0 text that was > > > > contradictory to or redundant with the text that I moved. > > > > Having those empty macro regions caused the compile to fail. > > > > It might be nice to have some way to flag the deleted text, > > > > with the convention, at least for now, of just commenting > > > > it out and not to delete it entirely from the file. > > > > > > > > Let me know if I am doing things right here and then I will > > > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > > > > > Bronis > > > > > > > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, > Bronis, > > > > > Rajeev, Jeff, and Alexander, > > > > > > > > > > you are responsible for one ore more chapters of MPI-2.1 until > the > > > > > meeting. > > > > > > > > > > It is a tough schedule: > > > > > ----------------------- > > > > > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token > is > > > > > logically passed to all chapter authors: > > > > > - You have read access to the source (via SVN) and the > > > pdf. > > > > > - You have write access to your local SVN copy. > > > > > - You will get write access to the SVN in a few days. > > > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > > > - This is a hard deadline (because I've to go on > travel) > > > > > * Sat., April 12, I will produce mpi-report.pdf as basis for > review > > > > > (I cannot do later, because April 14-17, I'm on travel) > > > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > > > * Fri., April 18, reviews - if necessary must be included - > > > > > by the chapter authors > > > > > * Sat., April 19, I will produce final mpi-report.pdf > > > > > which is basis for > > > > > - final reviews through the reviewer group > > > > > - official reading at the April 28-30, 2008 meeting. > > > > > (I cannot do later because I'm on travel April 20-26) > > > > > > > > > > The goals of your work as chapter author: > > > > > ----------------------------------------- > > > > > > > > > > - Remove references to MPI-1 and MPI-2. > > > > > - Substitute by MPI. > > > > > - Necessary modifications to achieve this goal. > > > > > > > > > > With this, we should have a single MPI-2.1 standard that does > > > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > > > > > ** This should be mainly a task in the area of > > > chapter-introductions. > > > > > ** Please, never change the wording of function definitions. > > > > > > > > > > Exceptions: > > > > > - There are routines that are deprecated and that are > > > > > already referenced in a consistent way. > > > > > My recommendation: > > > > > Current wording: > > > > > There are *new* function, and existing are now deprecated. > > > > > Proposal: > > > > > There are functions, and there exist also deprecated > functions > > > > > with (nearly) same functionality but deprecated due to some > > > lack > > > > > in the bindings (or functionality) > > > > > - There is history information in the frontmatter. > > > > > - there is a change-log annex with limited memory (only previous > > > version) > > > > > > > > > > Technical editing rule: > > > > > ----------------------- > > > > > > > > > > You must identify all of your changes: > > > > > > > > > > a) new/modified wording - you are highlighting your new/modified > > > wording with: > > > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > > modification > > > > > .... your modified / new wording .... > > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of > > > modification > > > > > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the > first > > > word > > > > > of the moved text with: > > > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > > text-move > > > > > First-word > > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing > > > text-move > > > > > ... rest of the moved text.... > > > > > % MPI-2.1 round-two - end of text-move > > > > > > > > > > Caution: These macros work only in black parts of the text. > > > > > > > > > > In blue parts you must substitute > > > > > \mpiiidotiMergeNEWforSINGLEendI% > > > > > by > > > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > > > > > The highlighting is done with red color. > > > > > (There are only a few other sentences from me magenta. > > > > > Therefore red should be the best to highlight the round-two > > > modifications.) > > > > > > > > > > Rsponsibilities: > > > > > ---------------- > > > > > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > > > * Acknowledgements credits.tex Rich Graham(text) + > > > Rolf(emails-auth.) > > > > > * 1. Introduction intro.tex Bill Gropp > > > > > - 2. Terms terms-2.tex Tony Skjellum > > > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > > > * 4. Collectives coll.tex Adam Moody > > > > > * 5. Groups, etc. context.tex Dick Treumann > > > > > - 6. Toplogies topol.tex Jesper Traeff > > > > > * 7. Environment inquiry.tex George Bosilca > > > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > > > - 9. Process Crea... dynamic-2.tex David Solt > > > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > > > - 12. IO io-2.tex Rajeev Thakur > > > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > > > - 14. Profiling prof.tex Bronis de Supinski > > > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander > Supalov > > > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > > > - Bibliography refs.bib Bill Gropp > > > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > > > only small work expected > > > > > * There was a significant merge, or new text, or ..., > > > > > more work expected > > > > > > > > > > I wish you a good start and good luck with your chapter. > > > > > > > > > > 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) > > > > > > > > > --------------------------------------------------------------------- > > > Intel GmbH > > > Dornacher Strasse 1 > > > 85622 Feldkirchen/Muenchen Germany > > > Sitz der Gesellschaft: Feldkirchen bei Muenchen > > > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > > > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > > > VAT Registration No.: DE129385895 > > > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > > > > > This e-mail and any attachments may contain confidential material > for > > > the sole use of the intended recipient(s). Any review or > distribution > > > by others is strictly prohibited. If you are not the intended > > > recipient, please contact the sender and delete all copies. > > > > > > > --------------------------------------------------------------------- > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen Germany > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > VAT Registration No.: DE129385895 > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > 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) From bronis at [hidden] Thu Apr 3 07:54:46 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Thu, 3 Apr 2008 05:54:46 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - delete text In-Reply-To: Message-ID: Rolf: The new macros work for me. No need to apologize, it's the normal start up on editing a big document. Thanks for fixing it so fast and checking in my changes. I already essentially followed your recommendation for deleted text so I won't check in a new version for that. I added the deleted text to removed_sources.tex as you requested in the attached. Bronis On Thu, 3 Apr 2008, Rolf Rabenseifner wrote: > My recommendation for really deleted text, i.e., > not only moved to another location: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you shoud add this outcommented text to the end of > removed_source.tex > > Best regards > Rolf > > > > On Wed, 2 Apr 2008 13:03:07 -0700 (PDT) > "Bronis R. de Supinski" wrote: > > It might be nice to have some way to flag the deleted text, > > with the convention, at least for now, of just commenting > > it out and not to delete it entirely from the file. > > > > Let me know if I am doing things right here and then I will > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > Bronis > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > > Rajeev, Jeff, and Alexander, > > > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > > meeting. > > > > > > It is a tough schedule: > > > ----------------------- > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > > logically passed to all chapter authors: > > > - You have read access to the source (via SVN) and the pdf. > > > - You have write access to your local SVN copy. > > > - You will get write access to the SVN in a few days. > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > - This is a hard deadline (because I've to go on travel) > > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > > (I cannot do later, because April 14-17, I'm on travel) > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > * Fri., April 18, reviews - if necessary must be included - > > > by the chapter authors > > > * Sat., April 19, I will produce final mpi-report.pdf > > > which is basis for > > > - final reviews through the reviewer group > > > - official reading at the April 28-30, 2008 meeting. > > > (I cannot do later because I'm on travel April 20-26) > > > > > > The goals of your work as chapter author: > > > ----------------------------------------- > > > > > > - Remove references to MPI-1 and MPI-2. > > > - Substitute by MPI. > > > - Necessary modifications to achieve this goal. > > > > > > With this, we should have a single MPI-2.1 standard that does > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > ** This should be mainly a task in the area of chapter-introductions. > > > ** Please, never change the wording of function definitions. > > > > > > Exceptions: > > > - There are routines that are deprecated and that are > > > already referenced in a consistent way. > > > My recommendation: > > > Current wording: > > > There are *new* function, and existing are now deprecated. > > > Proposal: > > > There are functions, and there exist also deprecated functions > > > with (nearly) same functionality but deprecated due to some lack > > > in the bindings (or functionality) > > > - There is history information in the frontmatter. > > > - there is a change-log annex with limited memory (only previous version) > > > > > > Technical editing rule: > > > ----------------------- > > > > > > You must identify all of your changes: > > > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > > .... your modified / new wording .... > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > > of the moved text with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > > First-word > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > > ... rest of the moved text.... > > > % MPI-2.1 round-two - end of text-move > > > > > > Caution: These macros work only in black parts of the text. > > > > > > In blue parts you must substitute > > > \mpiiidotiMergeNEWforSINGLEendI% > > > by > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > The highlighting is done with red color. > > > (There are only a few other sentences from me magenta. > > > Therefore red should be the best to highlight the round-two modifications.) > > > > > > Rsponsibilities: > > > ---------------- > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > > * 1. Introduction intro.tex Bill Gropp > > > - 2. Terms terms-2.tex Tony Skjellum > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > * 4. Collectives coll.tex Adam Moody > > > * 5. Groups, etc. context.tex Dick Treumann > > > - 6. Toplogies topol.tex Jesper Traeff > > > * 7. Environment inquiry.tex George Bosilca > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > - 9. Process Crea... dynamic-2.tex David Solt > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > - 12. IO io-2.tex Rajeev Thakur > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > - 14. Profiling prof.tex Bronis de Supinski > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > - Bibliography refs.bib Bill Gropp > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > only small work expected > > > * There was a significant merge, or new text, or ..., > > > more work expected > > > > > > I wish you a good start and good luck with your chapter. > > > > > > 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) > > > > > > > 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 > * -------------- next part -------------- A non-text attachment was scrubbed... Name: mpi-report.pdf Type: application/pdf Size: 3468217 bytes Desc: mpi-report.pdf URL: From rlgraham at [hidden] Thu Apr 3 10:47:14 2008 From: rlgraham at [hidden] (Richard Graham) Date: Thu, 03 Apr 2008 11:47:14 -0400 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: 2.1 we do expect to have a somewhat short lifetime, depending on what happens with MPI 2.2 and 3.0. However, this is the base for future revisions of the standard, so I think that it is worth slipping this schedule a bit so that we have a firm base to build on. The document will never be perfect, and this is not what we should strive for, but we should strive to have it be in a form that someone can pick up the document and implement the standard correctly. I will also add that I have talked with some who have committed to do a major portion of work for 2.1 who simply do not have the cycles to do this for several weeks. I am in the same situation. Rich On 4/3/08 8:09 AM, "Rolf Rabenseifner" wrote: > Hi all, > > yes, we need a decision as soon as possible. > > But first, it may be necessary to remove a wrong argument: > - The standard will have 6 month lifetime, not more! > - MPI 2.1 has to major goals: > - make Ballots 1-4 as part of the official standard, > - reduce the number of documents to one. > All rest is nice to have - not a major goal. > Until next Friday, only secure changes to intoductional text parts > should be done. More must be moved to MPI-2.2. > > To have a monolithic MPI standard document can be added to the agenda > of MPI-2.2. > > Here the official Scope of Effort as defined in January (see protocol): > > Scope of Effort: > - Clarification to the MPI standards document, > - resulting in a single document describing > the full MPI 2.1 standard. > - This includes merging of documents, text corrections, and added > clarifying text. > > All these three goals are achieved! > Current task is only to clean up small things, mainly (March protocol): > > Additional text-merge round with dedicated chapter authors. > Goal: > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > MPI-2.2 can do it better in 6 month. > The MPI-2.2 for this can start about 3 weeks after April meeting. > > I hope, you all can live with this decisions. > (My work time is limited; this is another reason why I cannot > accept a delay in the delivery of MPI-2.1) > > Bronis and George, > > my general statements do not answer you initial question: > If you decide to move parts from Chap.11 to Chap.7, > then you both mus discuss this. You both are responsible > for these chapters. > And you should first convince your reviewers: > - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > - Chap.11: Bill and Rainer > My recommendation: > Express clearly which parts should be moved exactly to wich line > (all based on page/line numbers as **printed** in Draft Apr. 1, 2008). > > Jeff, > > The idea of moving significant parts of Chap. 13 into Terms is > absolutely against the spirit of how this document is written. > The author tried to have only absolute necessary information > before the fist MPI example on page 25 (In MPI-1, it was page 16). > The MPI-2 Forum decided to put all the more detailed information > into extra sections, and especially binding stuff at the end of > the standard. > I put the Profiling behind Binding (this may be a fault). > > C and Fortran have the clear advantage that all constants > have the same name as the language-independently defined name, > e.g. MPI_COMM_WORLD, MPI_INT, MPI_SUCCESS... . > > For MPI-2.1, I would keep it as it is. > In MPI-2.2, there will be a longer discussion on C++ issues. > > Best regards > Rolf > > > On Thu, 3 Apr 2008 09:28:08 +0100 > "Supalov, Alexander" wrote: >> > Hi, >> > >> > Whatever the decision will be, we need it now. We're close to the point >> > of no return for the September deadline. >> > >> > Best regards. >> > >> > Alexander >> > >> > -----Original Message----- >> > From: Jesper Larsson Traeff [mailto:traff_at_it.neclab.eu] >> > Sent: Thursday, April 03, 2008 9:26 AM >> > To: Bronis R. de Supinski >> > Cc: Supalov, Alexander; Rolf Rabenseifner; William Gropp; Tony Skjellum; >> > Rich Graham; Adam Moody; Richard Treumann; George Bosilca; David Solt; >> > Rajeev Thakur; Jeff Squyres; MPI 2.1 Mailing List >> > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan >> > >> > >> > Dear All, >> > >> > I agree with the comments of Bronis about datatypes - functionality >> > that belongs together should be together in the STANDARD! (which is what >> > we >> > are writing). To me it seems that this 2.1 is somewhat more than the >> > "merge" it was optimistically intended to be. Since this, as Bronis >> > says, will likely be THE STANDARD for years to come, and the entry point >> > for many new users, I think it is important that we get it right the >> > first time, and I believe this is possible (if not, we should abort the >> > attempt). It's good to have strict deadlines, but let's not be fanatical >> > >> > about that. I don't see any purpose whatsoever in putting out >> > intermediate >> > versions of 2.1 - as long as we are in limbo, 1.3 and 2.0 will work >> > perfectly, they have all the ballots included >> > >> > I will try to send comments on/updates of my chapters (these will, >> > I think/hope, not need so much) tomorrow/monday >> > >> > best regards >> > >> > Jesper >> > >> > On Wed, Apr 02, 2008 at 02:26:13PM -0700, Bronis R. de Supinski wrote: >>> > > >>> > > All: >>> > > >>> > > I thoroughly agree with the sentiment that many expressed >>> > > that we are better off slipping the release of 2.1 two or >>> > > four months more in order to get it right than hurrying to >>> > > get it out the door. It is likely to be THE standard for >>> > > a fairly long time and having it broken to begin with does >>> > > not seem wise. >>> > > >>> > > Bronis >>> > > >>> > > >>> > > On Wed, 2 Apr 2008, Supalov, Alexander wrote: >>> > > >>>> > > > Hi, >>>> > > > >>>> > > > We may want to reduce the number of top level sections in the >> > standard. >>>> > > > In my opinion that I expressed to Rolf a couple of weeks ago, quite >> > a >>>> > > > few sections, like the ones mentioned by Bronis, should rather >> > belong to >>>> > > > a big Miscellany chapter rather than figure up there by themselves. >> > They >>>> > > > may also be merged/reformed, too. >>>> > > > >>>> > > > However, this is going to be a bigger change than envisioned >> > originally. >>>> > > > I wonder whether we should decide right away whether we can afford >> > this >>>> > > > now without slipping the planned MPI-2.1 delivery in September. A >>>> > > > possible way would be to fix small things now and do second pass of >>>> > > > major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. >>>> > > > >>>> > > > Best regards. >>>> > > > >>>> > > > Alexander >>>> > > > >>>> > > > -----Original Message----- >>>> > > > From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] >>>> > > > Sent: Wednesday, April 02, 2008 11:15 PM >>>> > > > To: Rolf Rabenseifner >>>> > > > Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard >>>> > > > Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev >>>> > > > Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List >>>> > > > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan >>>> > > > >>>> > > > >>>> > > > >>>> > > > Rolf: >>>> > > > >>>> > > > I have not gone through Chapter 11 thoroughly yet but I have >>>> > > > already noticed some major changes that I would suggest. >>>> > > > >>>> > > > First Section 11.6: "Decoding a Datatype" seems out of place >>>> > > > in the merged document. It would make sense to me to have all >>>> > > > of the datatype functions together. If we don't make datatypes >>>> > > > a separate chapter, then this section (11.6) should be moved >>>> > > > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, >>>> > > > it would be merged into that section since it is clearly part >>>> > > > of that functionality. >>>> > > > >>>> > > > Second, Section 11.5: "Error Classes, Error Codes, and Error >>>> > > > Handlers" is strongly related to Section 7.3: "Error Handling", >>>> > > > and Section 7.4: "Error Codes and Classes". Clearly, these >>>> > > > sections should be merged. In fact, this overlap makes me ask >>>> > > > why have we not merged Chapters 7 and 11? What is the difference >>>> > > > between "Environmental Management" and "External Interfaces"? >>>> > > > >>>> > > > I think this question needs to be resolved before I go further >>>> > > > on working on Chapter 11. Perhaps George and I should coordinate >>>> > > > merging these chapters after I coordinate moving the datatype >>>> > > > decoding functionality into chapter 3 with Rich... >>>> > > > >>>> > > > Bronis >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: >>>> > > > >>>>> > > > > >>>>> > > > > Rolf: >>>>> > > > > >>>>> > > > > I have finished editing chapter 14: Profiling. I have >>>>> > > > > attached the modified prof.tex since I do not yet have >>>>> > > > > write access. More importantly, either there is a problem >>>>> > > > > with the 2.1 macros or I am doing something wrong (I think >>>>> > > > > it is the first but I am not LaTex fluent enough to be >>>>> > > > > certain). Specifically, the first letter of the word >>>>> > > > > following the end markers does not appear in the generated >>>>> > > > > PDF. I would appreciate it if you could look into which it is. >>>>> > > > > >>>>> > > > > Another observation is that the macro does not work around >>>>> > > > > empty sections. In particular, I tried to mark the section >>>>> > > > > that I moved with the macros, with the original text commented >>>>> > > > > out. I tried to do the same for some MPI-1.0 text that was >>>>> > > > > contradictory to or redundant with the text that I moved. >>>>> > > > > Having those empty macro regions caused the compile to fail. >>>>> > > > > It might be nice to have some way to flag the deleted text, >>>>> > > > > with the convention, at least for now, of just commenting >>>>> > > > > it out and not to delete it entirely from the file. >>>>> > > > > >>>>> > > > > Let me know if I am doing things right here and then I will >>>>> > > > > move on to fixing chapter 11: External Interfaces. Thanks, >>>>> > > > > >>>>> > > > > Bronis >>>>> > > > > >>>>> > > > > >>>>> > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: >>>>> > > > > >>>>>> > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, >> > Bronis, >>>>>> > > > > > Rajeev, Jeff, and Alexander, >>>>>> > > > > > >>>>>> > > > > > you are responsible for one ore more chapters of MPI-2.1 until >> > the >>>>>> > > > > > meeting. >>>>>> > > > > > >>>>>> > > > > > It is a tough schedule: >>>>>> > > > > > ----------------------- >>>>>> > > > > > >>>>>> > > > > > * Tues, April 1, my ROUND ONE is finished and the write token >> > is >>>>>> > > > > > logically passed to all chapter authors: >>>>>> > > > > > - You have read access to the source (via SVN) and the >>>> > > > pdf. >>>>>> > > > > > - You have write access to your local SVN copy. >>>>>> > > > > > - You will get write access to the SVN in a few days. >>>>>> > > > > > * Fri., April 11, chapter authors have finished ROUND TWO. >>>>>> > > > > > - This is a hard deadline (because I've to go on >> > travel) >>>>>> > > > > > * Sat., April 12, I will produce mpi-report.pdf as basis for >> > review >>>>>> > > > > > (I cannot do later, because April 14-17, I'm on travel) >>>>>> > > > > > * Mon.-Thu., April 14-17, strong review by the reviewer group >>>>>> > > > > > * Fri., April 18, reviews - if necessary must be included - >>>>>> > > > > > by the chapter authors >>>>>> > > > > > * Sat., April 19, I will produce final mpi-report.pdf >>>>>> > > > > > which is basis for >>>>>> > > > > > - final reviews through the reviewer group >>>>>> > > > > > - official reading at the April 28-30, 2008 meeting. >>>>>> > > > > > (I cannot do later because I'm on travel April 20-26) >>>>>> > > > > > >>>>>> > > > > > The goals of your work as chapter author: >>>>>> > > > > > ----------------------------------------- >>>>>> > > > > > >>>>>> > > > > > - Remove references to MPI-1 and MPI-2. >>>>>> > > > > > - Substitute by MPI. >>>>>> > > > > > - Necessary modifications to achieve this goal. >>>>>> > > > > > >>>>>> > > > > > With this, we should have a single MPI-2.1 standard that does >>>>>> > > > > > not "know" the MPI-1 or MPI-2 history of individual functions. >>>>>> > > > > > >>>>>> > > > > > ** This should be mainly a task in the area of >>>> > > > chapter-introductions. >>>>>> > > > > > ** Please, never change the wording of function definitions. >>>>>> > > > > > >>>>>> > > > > > Exceptions: >>>>>> > > > > > - There are routines that are deprecated and that are >>>>>> > > > > > already referenced in a consistent way. >>>>>> > > > > > My recommendation: >>>>>> > > > > > Current wording: >>>>>> > > > > > There are *new* function, and existing are now deprecated. >>>>>> > > > > > Proposal: >>>>>> > > > > > There are functions, and there exist also deprecated >> > functions >>>>>> > > > > > with (nearly) same functionality but deprecated due to some >>>> > > > lack >>>>>> > > > > > in the bindings (or functionality) >>>>>> > > > > > - There is history information in the frontmatter. >>>>>> > > > > > - there is a change-log annex with limited memory (only previous >>>> > > > version) >>>>>> > > > > > >>>>>> > > > > > Technical editing rule: >>>>>> > > > > > ----------------------- >>>>>> > > > > > >>>>>> > > > > > You must identify all of your changes: >>>>>> > > > > > >>>>>> > > > > > a) new/modified wording - you are highlighting your >>>>>> new/modified >>>> > > > wording with: >>>>>> > > > > > >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >>>> > > > modification >>>>>> > > > > > .... your modified / new wording .... >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of >>>> > > > modification >>>>>> > > > > > >>>>>> > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the >> > first >>>> > > > word >>>>>> > > > > > of the moved text with: >>>>>> > > > > > >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >>>> > > > text-move >>>>>> > > > > > First-word >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing >>>> > > > text-move >>>>>> > > > > > ... rest of the moved text.... >>>>>> > > > > > % MPI-2.1 round-two - end of text-move >>>>>> > > > > > >>>>>> > > > > > Caution: These macros work only in black parts of the text. >>>>>> > > > > > >>>>>> > > > > > In blue parts you must substitute >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEendI% >>>>>> > > > > > by >>>>>> > > > > > \mpiiidotiMergeNEWforSINGLEendII% >>>>>> > > > > > >>>>>> > > > > > The highlighting is done with red color. >>>>>> > > > > > (There are only a few other sentences from me magenta. >>>>>> > > > > > Therefore red should be the best to highlight the round-two >>>> > > > modifications.) >>>>>> > > > > > >>>>>> > > > > > Rsponsibilities: >>>>>> > > > > > ---------------- >>>>>> > > > > > >>>>>> > > > > > * Frontmatter mpi-report.tex Bill Gropp >>>>>> > > > > > * Acknowledgements credits.tex Rich Graham(text) + >>>> > > > Rolf(emails-auth.) >>>>>> > > > > > * 1. Introduction intro.tex Bill Gropp >>>>>> > > > > > - 2. Terms terms-2.tex Tony Skjellum >>>>>> > > > > > * 3. Point-to-point pt2pt.tex Rich Graham >>>>>> > > > > > * 4. Collectives coll.tex Adam Moody >>>>>> > > > > > * 5. Groups, etc. context.tex Dick Treumann >>>>>> > > > > > - 6. Toplogies topol.tex Jesper Traeff >>>>>> > > > > > * 7. Environment inquiry.tex George Bosilca >>>>>> > > > > > - 8. Miscellany misc-2.tex Jesper Traeff >>>>>> > > > > > - 9. Process Crea... dynamic-2.tex David Solt >>>>>> > > > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff >>>>>> > > > > > - 11. External Int. ei-2.tex Bronis de Supinski >>>>>> > > > > > - 12. IO io-2.tex Rajeev Thakur >>>>>> > > > > > - 13. Lang.Binding binding-2.tex Jeff Squyres >>>>>> > > > > > - 14. Profiling prof.tex Bronis de Supinski >>>>>> > > > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner >>>>>> > > > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander >> > Supalov >>>>>> > > > > > - Annex B Change-log changes.tex Rolf Rabenseifner >>>>>> > > > > > - Bibliography refs.bib Bill Gropp >>>>>> > > > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner >>>>>> > > > > > >>>>>> > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, >>>>>> > > > > > only small work expected >>>>>> > > > > > * There was a significant merge, or new text, or ..., >>>>>> > > > > > more work expected >>>>>> > > > > > >>>>>> > > > > > I wish you a good start and good luck with your chapter. >>>>>> > > > > > >>>>>> > > > > > 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) >>>>>> > > > > > >>>> > > > >> > --------------------------------------------------------------------- >>>> > > > Intel GmbH >>>> > > > Dornacher Strasse 1 >>>> > > > 85622 Feldkirchen/Muenchen Germany >>>> > > > Sitz der Gesellschaft: Feldkirchen bei Muenchen >>>> > > > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer >>>> > > > Registergericht: Muenchen HRB 47456 Ust.-IdNr. >>>> > > > VAT Registration No.: DE129385895 >>>> > > > Citibank Frankfurt (BLZ 502 109 00) 600119052 >>>> > > > >>>> > > > This e-mail and any attachments may contain confidential material >> > for >>>> > > > the sole use of the intended recipient(s). Any review or >> > distribution >>>> > > > by others is strictly prohibited. If you are not the intended >>>> > > > recipient, please contact the sender and delete all copies. >>>> > > > >>>> > > > >> > --------------------------------------------------------------------- >> > Intel GmbH >> > Dornacher Strasse 1 >> > 85622 Feldkirchen/Muenchen Germany >> > Sitz der Gesellschaft: Feldkirchen bei Muenchen >> > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer >> > Registergericht: Muenchen HRB 47456 Ust.-IdNr. >> > VAT Registration No.: DE129385895 >> > Citibank Frankfurt (BLZ 502 109 00) 600119052 >> > >> > This e-mail and any attachments may contain confidential material for >> > the sole use of the intended recipient(s). Any review or distribution >> > by others is strictly prohibited. If you are not the intended >> > recipient, please contact the sender and delete all copies. >> > > > > > 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 > * -------------- next part -------------- An HTML attachment was scrubbed... URL: From rabenseifner at [hidden] Thu Apr 3 11:09:09 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 03 Apr 2008 18:09:09 +0200 Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org Message-ID: All C++ MPI specialists, which relevance has the MPI C++ binding of Boost ( http://www.boost.org/ )? In the actual version 1.35 http://www.boost.org/users/news/version_1_35_0 one can find a "C++-friendly interface to the standard Message Passing Interface". The comment from boost: "Although there exist C++ bindings for MPI, they offer little functionality over the C bindings." Is there any knowledge of whether in real C++ programming, whether the official C++ MPI binding or the C++ boost MPI binding is more often used in the C++ community? For me, the answer may have implications on how separate or integrated additional bindings should be integrated into the language independent text of the MPI standard. Best regards Rolf PS: As non-C++-specialist, this question is based on a question from Martin Bernreuther. The citations are from him. 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) From bronis at [hidden] Thu Apr 3 11:58:09 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Thu, 3 Apr 2008 09:58:09 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: Rolf: Re: > my general statements do not answer you initial question: My opinion is that leaving obvious problems unfixed based on an expected future version is a bad idea. However, I don't want to argue over this since I think the best approach is just to remove them now and then we don't have to worry about them. Others have more concerns over the time that they can devote to this (not that I have an abundance) and might want to delay in any event in order to get it right (at least mostly). > If you decide to move parts from Chap.11 to Chap.7, > then you both mus discuss this. You both are responsible > for these chapters. > And you should first convince your reviewers: > - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > - Chap.11: Bill and Rainer > My recommendation: > Express clearly which parts should be moved exactly to wich line > (all based on page/line numbers as **printed** in Draft Apr. 1, 2008). I have discussed moving the datatype decoding stuff with Rich and Bill. I will move those sections as I suggested, with an initial pass for the current review. This works well for Rich since he does not have time to do this for another couple of weeks. I hope to get that done today. For the remainder, I will look over the two chapters (7 & 11) and propose an initial merge strategy. George can react to that; I don't know how long it will take me to get that done... Bronis From erezh at [hidden] Thu Apr 3 13:01:28 2008 From: erezh at [hidden] (Erez Haba) Date: Thu, 3 Apr 2008 11:01:28 -0700 Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org In-Reply-To: Message-ID: <6B68D01C00C9994A8E150183E62A119E729E393581@NA-EXMSG-C105.redmond.corp.microsoft.com> Definitely the boost.mpi bindings are more useful; but I don't have the information if it is being used more. For example Microsoft does not ship the C++ bindings for several reason; (like compiler incompatibilities), but does point to boost.mpi as the C++ binding of choice. Thanks, .Erez -----Original Message----- From: mpi-21-bounces_at_[hidden] [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of Rolf Rabenseifner Sent: Thursday, April 03, 2008 9:09 AM To: MPI 2.1 Mailing List Cc: Martin Bernreuther Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org All C++ MPI specialists, which relevance has the MPI C++ binding of Boost ( http://www.boost.org/ )? In the actual version 1.35 http://www.boost.org/users/news/version_1_35_0 one can find a "C++-friendly interface to the standard Message Passing Interface". The comment from boost: "Although there exist C++ bindings for MPI, they offer little functionality over the C bindings." Is there any knowledge of whether in real C++ programming, whether the official C++ MPI binding or the C++ boost MPI binding is more often used in the C++ community? For me, the answer may have implications on how separate or integrated additional bindings should be integrated into the language independent text of the MPI standard. Best regards Rolf PS: As non-C++-specialist, this question is based on a question from Martin Bernreuther. The citations are from him. 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 From puri at [hidden] Thu Apr 3 13:17:47 2008 From: puri at [hidden] (Purushotham Bangalore) Date: Thu, 3 Apr 2008 13:17:47 -0500 (CDT) Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org In-Reply-To: Message-ID: <71987910.24261207246667069.JavaMail.root@zimbra.cis.uab.edu> The C++ developers that I know (not many) tend to use the C bindings instead of the C++ bindings or the Boost MPI. Puri ----- Original Message ----- From: "Rolf Rabenseifner" To: "MPI 2.1 Mailing List" Cc: "Martin Bernreuther" Sent: Thursday, April 3, 2008 11:09:09 AM (GMT-0600) America/Chicago Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org All C++ MPI specialists, which relevance has the MPI C++ binding of Boost ( http://www.boost.org/ )? In the actual version 1.35 http://www.boost.org/users/news/version_1_35_0 one can find a "C++-friendly interface to the standard Message Passing Interface". The comment from boost: "Although there exist C++ bindings for MPI, they offer little functionality over the C bindings." Is there any knowledge of whether in real C++ programming, whether the official C++ MPI binding or the C++ boost MPI binding is more often used in the C++ community? For me, the answer may have implications on how separate or integrated additional bindings should be integrated into the language independent text of the MPI standard. Best regards Rolf PS: As non-C++-specialist, this question is based on a question from Martin Bernreuther. The citations are from him. 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 From tony at [hidden] Thu Apr 3 13:46:57 2008 From: tony at [hidden] (Anthony Skjellum) Date: Thu, 3 Apr 2008 13:46:57 -0500 Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org In-Reply-To: <71987910.24261207246667069.JavaMail.root@zimbra.cis.uab.edu> Message-ID: The C bindings appear (moving forward) to support C, C++, and Fortran-2008. This is just one thing for people to learn. Tony On Apr 3, 2008, at 1:17 PM, Purushotham Bangalore wrote: > The C++ developers that I know (not many) tend to use the C > bindings instead of the C++ bindings or the Boost MPI. > > Puri > ----- Original Message ----- > From: "Rolf Rabenseifner" > To: "MPI 2.1 Mailing List" > Cc: "Martin Bernreuther" > Sent: Thursday, April 3, 2008 11:09:09 AM (GMT-0600) America/Chicago > Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org > > All C++ MPI specialists, > > which relevance has the MPI C++ binding of Boost ( http:// > www.boost.org/ )? > In the actual version 1.35 > http://www.boost.org/users/news/version_1_35_0 > one can find a "C++-friendly interface to the standard Message > Passing Interface". > > The comment from boost: > "Although there exist C++ bindings for MPI, they offer little > functionality over the C bindings." > > Is there any knowledge of whether in real C++ programming, whether > the official C++ MPI binding or the C++ boost MPI binding is > more often used in the C++ community? > > For me, the answer may have implications on how separate or integrated > additional bindings should be integrated into the language > independent text of the MPI standard. > > Best regards > Rolf > > PS: As non-C++-specialist, this question is based on a question from > Martin Bernreuther. The citations are from him. > > 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 -- The information contained in this communication may be confidential and is intended only for the use of the recipient(s) named above. If the reader of this communication is not the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you are not a named recipient or received this communication by mistake, please notify the sender and delete the communication and all copies of it. From jsquyres at [hidden] Thu Apr 3 14:13:10 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Thu, 3 Apr 2008 15:13:10 -0400 Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org In-Reply-To: Message-ID: On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: > Is there any knowledge of whether in real C++ programming, whether > the official C++ MPI binding or the C++ boost MPI binding is > more often used in the C++ community? Certainly, the boost bindings offer a much richer interface. However, I've certainly seen at least some users use the C++ bindings, if for nothing other than being able to use return values, such as: int rank = COMM_WORLD.Get_rank(); I've typically seen "C+" styles -- mixing the simple C++ constructs with C (or mostly C) applications. There are a few other advantages to the C++ bindings, too (e.g., references), but nothing that screams "you must use me!" to C++ programmers. That was actually the Forum's specific intent. Please remember (as has been mentioned several times already): the Forum explicitly decided not to standardize a rich C++ class library. The decision was specifically made to have C++ bindings that were a [mostly] 1-to-1 relationship with the language neutral bindings. If we had standardized a class library, it would have different semantics than the language neutral bindings, and therefore effectively be a whole second MPI standard. > For me, the answer may have implications on how separate or > integrated additional bindings should be integrated into the > language independent text of the MPI standard. I don't quite understand. All officially-supported language bindings should be listed consistently in the standard. In MPI-2.1, for example, that means alongside the language neutral bindings in the text and in Annex A. -- Jeff Squyres Cisco Systems From bosilca at [hidden] Thu Apr 3 14:19:55 2008 From: bosilca at [hidden] (George Bosilca) Date: Thu, 3 Apr 2008 15:19:55 -0400 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <57CC32C3-2884-4908-9D9A-80CE05A9397A@eecs.utk.edu> Bronis, If the data-type section get moved into the chapter 3 it make sense to merge the leftover of the chapter 11 with chapter 7, as long as we choose a right name. "MPI Environmental Management" is not the right chapter for "Generalized Requests". But of course these are just details. I'll get in touch with you asap to see how we can coordinate. Thanks, george. On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > > Rolf: > > Re: >> my general statements do not answer you initial question: > > My opinion is that leaving obvious problems unfixed based > on an expected future version is a bad idea. However, I > don't want to argue over this since I think the best > approach is just to remove them now and then we don't > have to worry about them. Others have more concerns over > the time that they can devote to this (not that I have an > abundance) and might want to delay in any event in order > to get it right (at least mostly). > >> If you decide to move parts from Chap.11 to Chap.7, >> then you both mus discuss this. You both are responsible >> for these chapters. >> And you should first convince your reviewers: >> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill >> - Chap.11: Bill and Rainer >> My recommendation: >> Express clearly which parts should be moved exactly to wich line >> (all based on page/line numbers as **printed** in Draft Apr. 1, >> 2008). > > I have discussed moving the datatype decoding stuff > with Rich and Bill. I will move those sections as I > suggested, with an initial pass for the current review. > This works well for Rich since he does not have time > to do this for another couple of weeks. I hope to get > that done today. > > For the remainder, I will look over the two chapters > (7 & 11) and propose an initial merge strategy. George > can react to that; I don't know how long it will take > me to get that done... > > Bronis > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 * -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2423 bytes Desc: smime.p7s URL: From alexander.supalov at [hidden] Thu Apr 3 14:23:46 2008 From: alexander.supalov at [hidden] (Supalov, Alexander) Date: Thu, 3 Apr 2008 20:23:46 +0100 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <57CC32C3-2884-4908-9D9A-80CE05A9397A@eecs.utk.edu> Message-ID: <5ECAB1304A8B5B4CB3F9D6C01E4E21A201360391@swsmsx413.ger.corp.intel.com> Hi guys, As soon as we start moving chapters, the binding annex may change as well. I need your updates soon to make sense of the annex. Best regards. Alexander -----Original Message----- From: mpi-21-bounces_at_[hidden] [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of George Bosilca Sent: Thursday, April 03, 2008 9:20 PM To: MPI 2.1 Mailing List Subject: Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan Bronis, If the data-type section get moved into the chapter 3 it make sense to merge the leftover of the chapter 11 with chapter 7, as long as we choose a right name. "MPI Environmental Management" is not the right chapter for "Generalized Requests". But of course these are just details. I'll get in touch with you asap to see how we can coordinate. Thanks, george. On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > > Rolf: > > Re: >> my general statements do not answer you initial question: > > My opinion is that leaving obvious problems unfixed based > on an expected future version is a bad idea. However, I > don't want to argue over this since I think the best > approach is just to remove them now and then we don't > have to worry about them. Others have more concerns over > the time that they can devote to this (not that I have an > abundance) and might want to delay in any event in order > to get it right (at least mostly). > >> If you decide to move parts from Chap.11 to Chap.7, >> then you both mus discuss this. You both are responsible >> for these chapters. >> And you should first convince your reviewers: >> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill >> - Chap.11: Bill and Rainer >> My recommendation: >> Express clearly which parts should be moved exactly to wich line >> (all based on page/line numbers as **printed** in Draft Apr. 1, >> 2008). > > I have discussed moving the datatype decoding stuff > with Rich and Bill. I will move those sections as I > suggested, with an initial pass for the current review. > This works well for Rich since he does not have time > to do this for another couple of weeks. I hope to get > that done today. > > For the remainder, I will look over the two chapters > (7 & 11) and propose an initial merge strategy. George > can react to that; I don't know how long it will take > me to get that done... > > Bronis > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 --------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen Germany Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr. VAT Registration No.: DE129385895 Citibank Frankfurt (BLZ 502 109 00) 600119052 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From jsquyres at [hidden] Thu Apr 3 14:27:08 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Thu, 3 Apr 2008 15:27:08 -0400 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <57CC32C3-2884-4908-9D9A-80CE05A9397A@eecs.utk.edu> Message-ID: <7A37D834-2769-437D-BBCD-9B8C07F9AF06@cisco.com> What about the C++/Fortran language bindings text? Should the majority of chapter 13 be merged into Terms and Conventions (and elsewhere)? It's not really a "problem", per se -- but it is a little awkward. There are sections in chapter 13 that could definitely fit in existing text elsewhere. Some of it is redundant, too. On Apr 3, 2008, at 3:19 PM, George Bosilca wrote: > Bronis, > > If the data-type section get moved into the chapter 3 it make sense > to merge the leftover of the chapter 11 with chapter 7, as long as > we choose a right name. "MPI Environmental Management" is not the > right chapter for "Generalized Requests". But of course these are > just details. > > I'll get in touch with you asap to see how we can coordinate. > > Thanks, > george. > > On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: >> >> Rolf: >> >> Re: >>> my general statements do not answer you initial question: >> >> My opinion is that leaving obvious problems unfixed based >> on an expected future version is a bad idea. However, I >> don't want to argue over this since I think the best >> approach is just to remove them now and then we don't >> have to worry about them. Others have more concerns over >> the time that they can devote to this (not that I have an >> abundance) and might want to delay in any event in order >> to get it right (at least mostly). >> >>> If you decide to move parts from Chap.11 to Chap.7, >>> then you both mus discuss this. You both are responsible >>> for these chapters. >>> And you should first convince your reviewers: >>> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill >>> - Chap.11: Bill and Rainer >>> My recommendation: >>> Express clearly which parts should be moved exactly to wich line >>> (all based on page/line numbers as **printed** in Draft Apr. 1, >>> 2008). >> >> I have discussed moving the datatype decoding stuff >> with Rich and Bill. I will move those sections as I >> suggested, with an initial pass for the current review. >> This works well for Rich since he does not have time >> to do this for another couple of weeks. I hope to get >> that done today. >> >> For the remainder, I will look over the two chapters >> (7 & 11) and propose an initial merge strategy. George >> can react to that; I don't know how long it will take >> me to get that done... >> >> Bronis >> >> _______________________________________________ >> 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 -- Jeff Squyres Cisco Systems From bronis at [hidden] Thu Apr 3 23:40:23 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Thu, 3 Apr 2008 21:40:23 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: Rich: Attached is the modified pt2pt.tex that incorporates the decoding datatypes section, with my changes to bring it into line with a single merged standard. The task was not simple since the section includes a list of type combiners including those for deprecated functions. I chose to leave them there but to modify the discussion to conform to that status... Rolf: I also attach my current versions of ei-2.tex and removed-sources.tex, which reflect the move of text into pt2pt.tex. Ordinarily, I would commit these at this point. That way, the repo would be consistent with the versions that George and I will need to use in order to merge chapters 7 & 11. Bronis On Thu, 3 Apr 2008, Bronis R. de Supinski wrote: > > Rolf: > > Re: > > my general statements do not answer you initial question: > > My opinion is that leaving obvious problems unfixed based > on an expected future version is a bad idea. However, I > don't want to argue over this since I think the best > approach is just to remove them now and then we don't > have to worry about them. Others have more concerns over > the time that they can devote to this (not that I have an > abundance) and might want to delay in any event in order > to get it right (at least mostly). > > > If you decide to move parts from Chap.11 to Chap.7, > > then you both mus discuss this. You both are responsible > > for these chapters. > > And you should first convince your reviewers: > > - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > > - Chap.11: Bill and Rainer > > My recommendation: > > Express clearly which parts should be moved exactly to wich line > > (all based on page/line numbers as **printed** in Draft Apr. 1, 2008). > > I have discussed moving the datatype decoding stuff > with Rich and Bill. I will move those sections as I > suggested, with an initial pass for the current review. > This works well for Rich since he does not have time > to do this for another couple of weeks. I hope to get > that done today. > > For the remainder, I will look over the two chapters > (7 & 11) and propose an initial merge strategy. George > can react to that; I don't know how long it will take > me to get that done... > > Bronis > > * -------------- next part -------------- A non-text attachment was scrubbed... Name: removed_sources.tex Type: application/x-tex Size: 57072 bytes Desc: removed_sources.tex URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ei-2.tex Type: application/x-tex Size: 94382 bytes Desc: ei-2.tex URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pt2pt.tex Type: application/x-tex Size: 323007 bytes Desc: pt2pt.tex URL: From rabenseifner at [hidden] Fri Apr 4 05:15:43 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 12:15:43 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - delete text In-Reply-To: Message-ID: All authors, to make it clear: removed_sources.tex is only for text that is really deleted, i.e., text that was in MPI-1.1 or MPI-2, but that is *not* in MPI-2.1. Please do not put any moved text to this file. Thanks Rolf On Thu, 03 Apr 2008 13:13:43 +0200 "Rolf Rabenseifner" wrote: > My recommendation for really deleted text, i.e., > not only moved to another location: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you shoud add this outcommented text to the end of > removed_source.tex > > Best regards > Rolf > > > > On Wed, 2 Apr 2008 13:03:07 -0700 (PDT) > "Bronis R. de Supinski" wrote: > > It might be nice to have some way to flag the deleted text, > > with the convention, at least for now, of just commenting > > it out and not to delete it entirely from the file. > > > > Let me know if I am doing things right here and then I will > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > Bronis > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > > Rajeev, Jeff, and Alexander, > > > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > > meeting. > > > > > > It is a tough schedule: > > > ----------------------- > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > > logically passed to all chapter authors: > > > - You have read access to the source (via SVN) and the pdf. > > > - You have write access to your local SVN copy. > > > - You will get write access to the SVN in a few days. > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > - This is a hard deadline (because I've to go on travel) > > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > > (I cannot do later, because April 14-17, I'm on travel) > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > * Fri., April 18, reviews - if necessary must be included - > > > by the chapter authors > > > * Sat., April 19, I will produce final mpi-report.pdf > > > which is basis for > > > - final reviews through the reviewer group > > > - official reading at the April 28-30, 2008 meeting. > > > (I cannot do later because I'm on travel April 20-26) > > > > > > The goals of your work as chapter author: > > > ----------------------------------------- > > > > > > - Remove references to MPI-1 and MPI-2. > > > - Substitute by MPI. > > > - Necessary modifications to achieve this goal. > > > > > > With this, we should have a single MPI-2.1 standard that does > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > ** This should be mainly a task in the area of chapter-introductions. > > > ** Please, never change the wording of function definitions. > > > > > > Exceptions: > > > - There are routines that are deprecated and that are > > > already referenced in a consistent way. > > > My recommendation: > > > Current wording: > > > There are *new* function, and existing are now deprecated. > > > Proposal: > > > There are functions, and there exist also deprecated functions > > > with (nearly) same functionality but deprecated due to some lack > > > in the bindings (or functionality) > > > - There is history information in the frontmatter. > > > - there is a change-log annex with limited memory (only previous version) > > > > > > Technical editing rule: > > > ----------------------- > > > > > > You must identify all of your changes: > > > > > > a) new/modified wording - you are highlighting your new/modified wording with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > > > .... your modified / new wording .... > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > > > of the moved text with: > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > > > First-word > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > > > ... rest of the moved text.... > > > % MPI-2.1 round-two - end of text-move > > > > > > Caution: These macros work only in black parts of the text. > > > > > > In blue parts you must substitute > > > \mpiiidotiMergeNEWforSINGLEendI% > > > by > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > The highlighting is done with red color. > > > (There are only a few other sentences from me magenta. > > > Therefore red should be the best to highlight the round-two modifications.) > > > > > > Rsponsibilities: > > > ---------------- > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > > > * 1. Introduction intro.tex Bill Gropp > > > - 2. Terms terms-2.tex Tony Skjellum > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > * 4. Collectives coll.tex Adam Moody > > > * 5. Groups, etc. context.tex Dick Treumann > > > - 6. Toplogies topol.tex Jesper Traeff > > > * 7. Environment inquiry.tex George Bosilca > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > - 9. Process Crea... dynamic-2.tex David Solt > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > - 12. IO io-2.tex Rajeev Thakur > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > - 14. Profiling prof.tex Bronis de Supinski > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > - Bibliography refs.bib Bill Gropp > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > only small work expected > > > * There was a significant merge, or new text, or ..., > > > more work expected > > > > > > I wish you a good start and good luck with your chapter. > > > > > > 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) > > > > > > > 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 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) From rabenseifner at [hidden] Fri Apr 4 09:48:42 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 16:48:42 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <7A37D834-2769-437D-BBCD-9B8C07F9AF06@cisco.com> Message-ID: About Chap. 13, especially C++. I'm proposing (referencec to MPI-2.1 Draft Apr.1, 2008): - The MPI-2 Forum decided to put only small overview stuff into Chap. 2 Terms. (I want to recall, that in MPI-2 the Terms are rewritten for whole MPI, i.e., still valid in MPI-2.1) - The MPI-2 Forum decided to put all deeper information into extra sections of an additionally last chapter on Bindings. - The MPI-2 Forum already decided that normal C++ bindings should be after the Fortran bindings. - Terms, page 18, lines 36-39 clearly expresses, that all constants are given only in MPI_ notation and that C++ names (with MPI::) are given in Annex A. I.e., MPI_COMM_WORLD, MPI_FLOAT, MPI_PROC_NULL, ... should not to be translated everywhere in the chapters. Same for Table 3.2 on page 27. - There are important things were C++ clearly differs from C, e.g. the handling of the Status. I have already added the Status handling, see page 31 lines 23-32. (By the way, this information was missing in Chap. 13.1 and only available in the Annex A.) - I'm not aware, whether there are more such stuff, that is explained for C and Fortran and should be also explained for C++. Do you see an additional stuff like status? - I do not expect that it would be a good idee to move all the ugly Fortran problems (17 pages) to the beginning of thee book into Chap. 2 Terms. I would recommend same rule for C++ (12 pages). Chap.2 terms has only 16 pages - with 2 pages dedicated to Fortran, 1/2 page to C, and 3 pages to C++. Best regards Rolf On Thu, 3 Apr 2008 15:13:10 -0400 Jeff Squyres wrote: > On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: ... > > For me, the answer may have implications on how separate or > > integrated additional bindings should be integrated into the > > language independent text of the MPI standard. > > I don't quite understand. All officially-supported language bindings > should be listed consistently in the standard. In MPI-2.1, for > example, that means alongside the language neutral bindings in the > text and in Annex A. ------------- On Thu, 3 Apr 2008 15:27:08 -0400 Jeff Squyres wrote: > What about the C++/Fortran language bindings text? Should the > majority of chapter 13 be merged into Terms and Conventions (and > elsewhere)? > > It's not really a "problem", per se -- but it is a little awkward. > There are sections in chapter 13 that could definitely fit in existing > text elsewhere. Some of it is redundant, too. > > > > On Apr 3, 2008, at 3:19 PM, George Bosilca wrote: > > Bronis, > > > > If the data-type section get moved into the chapter 3 it make sense > > to merge the leftover of the chapter 11 with chapter 7, as long as > > we choose a right name. "MPI Environmental Management" is not the > > right chapter for "Generalized Requests". But of course these are > > just details. > > > > I'll get in touch with you asap to see how we can coordinate. > > > > Thanks, > > george. > > > > On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > >> > >> Rolf: > >> > >> Re: > >>> my general statements do not answer you initial question: > >> > >> My opinion is that leaving obvious problems unfixed based > >> on an expected future version is a bad idea. However, I > >> don't want to argue over this since I think the best > >> approach is just to remove them now and then we don't > >> have to worry about them. Others have more concerns over > >> the time that they can devote to this (not that I have an > >> abundance) and might want to delay in any event in order > >> to get it right (at least mostly). > >> > >>> If you decide to move parts from Chap.11 to Chap.7, > >>> then you both mus discuss this. You both are responsible > >>> for these chapters. > >>> And you should first convince your reviewers: > >>> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > >>> - Chap.11: Bill and Rainer > >>> My recommendation: > >>> Express clearly which parts should be moved exactly to wich line > >>> (all based on page/line numbers as **printed** in Draft Apr. 1, > >>> 2008). > >> > >> I have discussed moving the datatype decoding stuff > >> with Rich and Bill. I will move those sections as I > >> suggested, with an initial pass for the current review. > >> This works well for Rich since he does not have time > >> to do this for another couple of weeks. I hope to get > >> that done today. > >> > >> For the remainder, I will look over the two chapters > >> (7 & 11) and propose an initial merge strategy. George > >> can react to that; I don't know how long it will take > >> me to get that done... > >> > >> Bronis > >> > >> _______________________________________________ > >> 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 > > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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) From rabenseifner at [hidden] Fri Apr 4 09:58:35 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 16:58:35 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: Looks fine. Stored and commited in the SVN. Best regards Rolf On Thu, 3 Apr 2008 21:40:23 -0700 (PDT) "Bronis R. de Supinski" wrote: > > Rich: > > Attached is the modified pt2pt.tex that incorporates > the decoding datatypes section, with my changes to > bring it into line with a single merged standard. The > task was not simple since the section includes a list > of type combiners including those for deprecated > functions. I chose to leave them there but to modify > the discussion to conform to that status... > > Rolf: > > I also attach my current versions of ei-2.tex and > removed-sources.tex, which reflect the move of text > into pt2pt.tex. Ordinarily, I would commit these at > this point. That way, the repo would be consistent > with the versions that George and I will need to > use in order to merge chapters 7 & 11. > > Bronis > > > > On Thu, 3 Apr 2008, Bronis R. de Supinski wrote: > > > > > Rolf: > > > > Re: > > > my general statements do not answer you initial question: > > > > My opinion is that leaving obvious problems unfixed based > > on an expected future version is a bad idea. However, I > > don't want to argue over this since I think the best > > approach is just to remove them now and then we don't > > have to worry about them. Others have more concerns over > > the time that they can devote to this (not that I have an > > abundance) and might want to delay in any event in order > > to get it right (at least mostly). > > > > > If you decide to move parts from Chap.11 to Chap.7, > > > then you both mus discuss this. You both are responsible > > > for these chapters. > > > And you should first convince your reviewers: > > > - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > > > - Chap.11: Bill and Rainer > > > My recommendation: > > > Express clearly which parts should be moved exactly to wich line > > > (all based on page/line numbers as **printed** in Draft Apr. 1, 2008). > > > > I have discussed moving the datatype decoding stuff > > with Rich and Bill. I will move those sections as I > > suggested, with an initial pass for the current review. > > This works well for Rich since he does not have time > > to do this for another couple of weeks. I hope to get > > that done today. > > > > For the remainder, I will look over the two chapters > > (7 & 11) and propose an initial merge strategy. George > > can react to that; I don't know how long it will take > > me to get that done... > > > > Bronis > > > > 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) From rabenseifner at [hidden] Fri Apr 4 10:09:55 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 17:09:55 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <5ECAB1304A8B5B4CB3F9D6C01E4E21A201360391@swsmsx413.ger.corp.intel.com> Message-ID: Alexander, this isn't a problem: Annex A.1 is about constants: These must not change, because in this round-two, it is absolutly forbidden to change the standard content. Annex A.2-4 is done automatically, with one exception: If a whole chapter is removed or added, we must remove/add a line in MAKE-APPLANG (in lines 6-18). If a chapter title is changed, we have to modify such a line. That is all and easy, because Denis and his predecessor had made a good job. Best regards Rolf On Thu, 3 Apr 2008 20:23:46 +0100 "Supalov, Alexander" wrote: > Hi guys, > > As soon as we start moving chapters, the binding annex may change as > well. I need your updates soon to make sense of the annex. > > Best regards. > > Alexander > > -----Original Message----- > From: mpi-21-bounces_at_[hidden] > [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of George Bosilca > Sent: Thursday, April 03, 2008 9:20 PM > To: MPI 2.1 Mailing List > Subject: Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan > > Bronis, > > If the data-type section get moved into the chapter 3 it make sense to > merge the leftover of the chapter 11 with chapter 7, as long as we > choose a right name. "MPI Environmental Management" is not the right > chapter for "Generalized Requests". But of course these are just > details. > > I'll get in touch with you asap to see how we can coordinate. > > Thanks, > george. > > On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > > > > Rolf: > > > > Re: > >> my general statements do not answer you initial question: > > > > My opinion is that leaving obvious problems unfixed based > > on an expected future version is a bad idea. However, I > > don't want to argue over this since I think the best > > approach is just to remove them now and then we don't > > have to worry about them. Others have more concerns over > > the time that they can devote to this (not that I have an > > abundance) and might want to delay in any event in order > > to get it right (at least mostly). > > > >> If you decide to move parts from Chap.11 to Chap.7, > >> then you both mus discuss this. You both are responsible > >> for these chapters. > >> And you should first convince your reviewers: > >> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > >> - Chap.11: Bill and Rainer > >> My recommendation: > >> Express clearly which parts should be moved exactly to wich line > >> (all based on page/line numbers as **printed** in Draft Apr. 1, > >> 2008). > > > > I have discussed moving the datatype decoding stuff > > with Rich and Bill. I will move those sections as I > > suggested, with an initial pass for the current review. > > This works well for Rich since he does not have time > > to do this for another couple of weeks. I hope to get > > that done today. > > > > For the remainder, I will look over the two chapters > > (7 & 11) and propose an initial merge strategy. George > > can react to that; I don't know how long it will take > > me to get that done... > > > > Bronis > > > > _______________________________________________ > > mpi-21 mailing list > > mpi-21_at_[hidden] > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > --------------------------------------------------------------------- > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen Germany > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > VAT Registration No.: DE129385895 > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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) From alexander.supalov at [hidden] Fri Apr 4 10:31:00 2008 From: alexander.supalov at [hidden] (Supalov, Alexander) Date: Fri, 4 Apr 2008 16:31:00 +0100 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <5ECAB1304A8B5B4CB3F9D6C01E4E21A20136081F@swsmsx413.ger.corp.intel.com> Thanks. What I mean mostly is that the appendix can only be finalized, verified, and signed off on after all other chapters. This means we need to target April 10 to have the document really ready by April 11. The time zone difference plays against us here. -----Original Message----- From: mpi-21-bounces_at_[hidden] [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of Rolf Rabenseifner Sent: Friday, April 04, 2008 5:10 PM To: MPI 2.1 Mailing List Subject: Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan Alexander, this isn't a problem: Annex A.1 is about constants: These must not change, because in this round-two, it is absolutly forbidden to change the standard content. Annex A.2-4 is done automatically, with one exception: If a whole chapter is removed or added, we must remove/add a line in MAKE-APPLANG (in lines 6-18). If a chapter title is changed, we have to modify such a line. That is all and easy, because Denis and his predecessor had made a good job. Best regards Rolf On Thu, 3 Apr 2008 20:23:46 +0100 "Supalov, Alexander" wrote: > Hi guys, > > As soon as we start moving chapters, the binding annex may change as > well. I need your updates soon to make sense of the annex. > > Best regards. > > Alexander > > -----Original Message----- > From: mpi-21-bounces_at_[hidden] > [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of George Bosilca > Sent: Thursday, April 03, 2008 9:20 PM > To: MPI 2.1 Mailing List > Subject: Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan > > Bronis, > > If the data-type section get moved into the chapter 3 it make sense to > merge the leftover of the chapter 11 with chapter 7, as long as we > choose a right name. "MPI Environmental Management" is not the right > chapter for "Generalized Requests". But of course these are just > details. > > I'll get in touch with you asap to see how we can coordinate. > > Thanks, > george. > > On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > > > > Rolf: > > > > Re: > >> my general statements do not answer you initial question: > > > > My opinion is that leaving obvious problems unfixed based > > on an expected future version is a bad idea. However, I > > don't want to argue over this since I think the best > > approach is just to remove them now and then we don't > > have to worry about them. Others have more concerns over > > the time that they can devote to this (not that I have an > > abundance) and might want to delay in any event in order > > to get it right (at least mostly). > > > >> If you decide to move parts from Chap.11 to Chap.7, > >> then you both mus discuss this. You both are responsible > >> for these chapters. > >> And you should first convince your reviewers: > >> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > >> - Chap.11: Bill and Rainer > >> My recommendation: > >> Express clearly which parts should be moved exactly to wich line > >> (all based on page/line numbers as **printed** in Draft Apr. 1, > >> 2008). > > > > I have discussed moving the datatype decoding stuff > > with Rich and Bill. I will move those sections as I > > suggested, with an initial pass for the current review. > > This works well for Rich since he does not have time > > to do this for another couple of weeks. I hope to get > > that done today. > > > > For the remainder, I will look over the two chapters > > (7 & 11) and propose an initial merge strategy. George > > can react to that; I don't know how long it will take > > me to get that done... > > > > Bronis > > > > _______________________________________________ > > mpi-21 mailing list > > mpi-21_at_[hidden] > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > --------------------------------------------------------------------- > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen Germany > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > VAT Registration No.: DE129385895 > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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 --------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen Germany Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr. VAT Registration No.: DE129385895 Citibank Frankfurt (BLZ 502 109 00) 600119052 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From rabenseifner at [hidden] Fri Apr 4 11:55:58 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 18:55:58 +0200 Subject: [Mpi-21] AUTHORS of MPI-2.1 - New directory structure In-Reply-To: Message-ID: Dear author, for preparing write-access, I have moved (not changed) the sources. please be absolutely careful when makeing svn update Please be sure that if you have modified your source, that it is not overwritten (okay, i know that svn is itself very careful :-) * General structure _ mpi-report.tex _______________ Rolf Rabenseifner mpi-macs.tex * Frontmatter _______ chap-frontm/abstract-cpy.tex _ Bill Gropp chap-frontm/history.tex * Acknowledgements __ chap-frontm/credits.tex ______ Rich Graham(text) + Rolf(emails-auth.) * 1. Introduction ___ chap-intro/intro.tex _________ Bill Gropp - 2. Terms __________ chap-terms/terms-2.tex _______ Tony Skjellum * 3. Point-to-point _ chap-pt2pt/pt2pt.tex _________ Rich Graham * 4. Collectives ____ chap-coll/coll.tex ___________ Adam Moody * 5. Groups, etc. ___ chap-context/context.tex _____ Dick Treumann - 6. Toplogies ______ chap-topol/topol.tex _________ Jesper Traeff * 7. Environment ____ chap-inquiry/inquiry.tex _____ George Bosilca - 8. Miscellany _____ chap-misc/misc-2.tex _________ Jesper Traeff - 9. Process Crea.... chap-dynamic/dynamic-2.tex ___ David Solt - 10. One-sided Comm. chap-one-side/one-side-2.tex _ Jepser Traeff - 11. External Inter. chap-ei/ei-2.tex _____________ Bronis de Supinski - 12. IO ____________ chap-io/io-2.tex _____________ Rajeev Thakur - 13. Lang.Binding __ chap-binding/binding-2.tex ___ Jeff Squyres - 14. Profiling _____ chap-prof/prof.tex ___________ Bronis de Supinski - 15. Deprecated ____ chap-deprecated/deprecated.tex Rolf Rabenseifner - Annex A Lang.Bindi. chap-appLang/appLang-Const.tex Alexander Supalov MAKE-APPLANG & appLang*.tex __ Rolf Rabenseifner - Annex B Change-log. chap-changes/changes.tex _____ Rolf Rabenseifner - Bibliography ______ refs.bib _____________________ Bill Gropp - Index _____________ MAKE-FUNC-INDEX ______________ Rolf Rabenseifner Please make the svn update and check that make still produces mpi-report.pdf 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) From rabenseifner at [hidden] Fri Apr 4 12:21:11 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 04 Apr 2008 19:21:11 +0200 Subject: [Mpi-21] AUTHORS of MPI-2.1 - SVN rules In-Reply-To: Message-ID: Dear author, please commit with the following command (if your working directory is MPI-2.1): svn commit chap-xxx/xxx.tex -m 'MPI-2.1 - your-fiirst+last-name - summary, what you have done' svn update Please, inform also all via the mailing list, what you have done. Do we need any further rule? I'll try to put periodically copies of mpi-report.pdf on the web: http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf Username and password as usual: mpi21 and mpi21 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) From traff at [hidden] Thu Apr 3 02:25:51 2008 From: traff at [hidden] (Jesper Larsson Traeff) Date: Thu, 3 Apr 2008 09:25:51 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <20080403072551.GA15320@fourier.it.neclab.eu> Dear All, I agree with the comments of Bronis about datatypes - functionality that belongs together should be together in the STANDARD! (which is what we are writing). To me it seems that this 2.1 is somewhat more than the "merge" it was optimistically intended to be. Since this, as Bronis says, will likely be THE STANDARD for years to come, and the entry point for many new users, I think it is important that we get it right the first time, and I believe this is possible (if not, we should abort the attempt). It's good to have strict deadlines, but let's not be fanatical about that. I don't see any purpose whatsoever in putting out intermediate versions of 2.1 - as long as we are in limbo, 1.3 and 2.0 will work perfectly, they have all the ballots included I will try to send comments on/updates of my chapters (these will, I think/hope, not need so much) tomorrow/monday best regards Jesper On Wed, Apr 02, 2008 at 02:26:13PM -0700, Bronis R. de Supinski wrote: > > All: > > I thoroughly agree with the sentiment that many expressed > that we are better off slipping the release of 2.1 two or > four months more in order to get it right than hurrying to > get it out the door. It is likely to be THE standard for > a fairly long time and having it broken to begin with does > not seem wise. > > Bronis > > > On Wed, 2 Apr 2008, Supalov, Alexander wrote: > > > Hi, > > > > We may want to reduce the number of top level sections in the standard. > > In my opinion that I expressed to Rolf a couple of weeks ago, quite a > > few sections, like the ones mentioned by Bronis, should rather belong to > > a big Miscellany chapter rather than figure up there by themselves. They > > may also be merged/reformed, too. > > > > However, this is going to be a bigger change than envisioned originally. > > I wonder whether we should decide right away whether we can afford this > > now without slipping the planned MPI-2.1 delivery in September. A > > possible way would be to fix small things now and do second pass of > > major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. > > > > Best regards. > > > > Alexander > > > > -----Original Message----- > > From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] > > Sent: Wednesday, April 02, 2008 11:15 PM > > To: Rolf Rabenseifner > > Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard > > Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev > > Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List > > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan > > > > > > > > Rolf: > > > > I have not gone through Chapter 11 thoroughly yet but I have > > already noticed some major changes that I would suggest. > > > > First Section 11.6: "Decoding a Datatype" seems out of place > > in the merged document. It would make sense to me to have all > > of the datatype functions together. If we don't make datatypes > > a separate chapter, then this section (11.6) should be moved > > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, > > it would be merged into that section since it is clearly part > > of that functionality. > > > > Second, Section 11.5: "Error Classes, Error Codes, and Error > > Handlers" is strongly related to Section 7.3: "Error Handling", > > and Section 7.4: "Error Codes and Classes". Clearly, these > > sections should be merged. In fact, this overlap makes me ask > > why have we not merged Chapters 7 and 11? What is the difference > > between "Environmental Management" and "External Interfaces"? > > > > I think this question needs to be resolved before I go further > > on working on Chapter 11. Perhaps George and I should coordinate > > merging these chapters after I coordinate moving the datatype > > decoding functionality into chapter 3 with Rich... > > > > Bronis > > > > > > > > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > > > > > > > Rolf: > > > > > > I have finished editing chapter 14: Profiling. I have > > > attached the modified prof.tex since I do not yet have > > > write access. More importantly, either there is a problem > > > with the 2.1 macros or I am doing something wrong (I think > > > it is the first but I am not LaTex fluent enough to be > > > certain). Specifically, the first letter of the word > > > following the end markers does not appear in the generated > > > PDF. I would appreciate it if you could look into which it is. > > > > > > Another observation is that the macro does not work around > > > empty sections. In particular, I tried to mark the section > > > that I moved with the macros, with the original text commented > > > out. I tried to do the same for some MPI-1.0 text that was > > > contradictory to or redundant with the text that I moved. > > > Having those empty macro regions caused the compile to fail. > > > It might be nice to have some way to flag the deleted text, > > > with the convention, at least for now, of just commenting > > > it out and not to delete it entirely from the file. > > > > > > Let me know if I am doing things right here and then I will > > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > > > Bronis > > > > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > > > Rajeev, Jeff, and Alexander, > > > > > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > > > meeting. > > > > > > > > It is a tough schedule: > > > > ----------------------- > > > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > > > logically passed to all chapter authors: > > > > - You have read access to the source (via SVN) and the > > pdf. > > > > - You have write access to your local SVN copy. > > > > - You will get write access to the SVN in a few days. > > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > > - This is a hard deadline (because I've to go on travel) > > > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > > > (I cannot do later, because April 14-17, I'm on travel) > > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > > * Fri., April 18, reviews - if necessary must be included - > > > > by the chapter authors > > > > * Sat., April 19, I will produce final mpi-report.pdf > > > > which is basis for > > > > - final reviews through the reviewer group > > > > - official reading at the April 28-30, 2008 meeting. > > > > (I cannot do later because I'm on travel April 20-26) > > > > > > > > The goals of your work as chapter author: > > > > ----------------------------------------- > > > > > > > > - Remove references to MPI-1 and MPI-2. > > > > - Substitute by MPI. > > > > - Necessary modifications to achieve this goal. > > > > > > > > With this, we should have a single MPI-2.1 standard that does > > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > > > ** This should be mainly a task in the area of > > chapter-introductions. > > > > ** Please, never change the wording of function definitions. > > > > > > > > Exceptions: > > > > - There are routines that are deprecated and that are > > > > already referenced in a consistent way. > > > > My recommendation: > > > > Current wording: > > > > There are *new* function, and existing are now deprecated. > > > > Proposal: > > > > There are functions, and there exist also deprecated functions > > > > with (nearly) same functionality but deprecated due to some > > lack > > > > in the bindings (or functionality) > > > > - There is history information in the frontmatter. > > > > - there is a change-log annex with limited memory (only previous > > version) > > > > > > > > Technical editing rule: > > > > ----------------------- > > > > > > > > You must identify all of your changes: > > > > > > > > a) new/modified wording - you are highlighting your new/modified > > wording with: > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > modification > > > > .... your modified / new wording .... > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of > > modification > > > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first > > word > > > > of the moved text with: > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > text-move > > > > First-word > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing > > text-move > > > > ... rest of the moved text.... > > > > % MPI-2.1 round-two - end of text-move > > > > > > > > Caution: These macros work only in black parts of the text. > > > > > > > > In blue parts you must substitute > > > > \mpiiidotiMergeNEWforSINGLEendI% > > > > by > > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > > > The highlighting is done with red color. > > > > (There are only a few other sentences from me magenta. > > > > Therefore red should be the best to highlight the round-two > > modifications.) > > > > > > > > Rsponsibilities: > > > > ---------------- > > > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > > * Acknowledgements credits.tex Rich Graham(text) + > > Rolf(emails-auth.) > > > > * 1. Introduction intro.tex Bill Gropp > > > > - 2. Terms terms-2.tex Tony Skjellum > > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > > * 4. Collectives coll.tex Adam Moody > > > > * 5. Groups, etc. context.tex Dick Treumann > > > > - 6. Toplogies topol.tex Jesper Traeff > > > > * 7. Environment inquiry.tex George Bosilca > > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > > - 9. Process Crea... dynamic-2.tex David Solt > > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > > - 12. IO io-2.tex Rajeev Thakur > > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > > - 14. Profiling prof.tex Bronis de Supinski > > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > > - Bibliography refs.bib Bill Gropp > > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > > only small work expected > > > > * There was a significant merge, or new text, or ..., > > > > more work expected > > > > > > > > I wish you a good start and good luck with your chapter. > > > > > > > > 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) > > > > > > --------------------------------------------------------------------- > > Intel GmbH > > Dornacher Strasse 1 > > 85622 Feldkirchen/Muenchen Germany > > Sitz der Gesellschaft: Feldkirchen bei Muenchen > > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > > VAT Registration No.: DE129385895 > > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > > > This e-mail and any attachments may contain confidential material for > > the sole use of the intended recipient(s). Any review or distribution > > by others is strictly prohibited. If you are not the intended > > recipient, please contact the sender and delete all copies. > > > > From alexander.supalov at [hidden] Thu Apr 3 03:28:08 2008 From: alexander.supalov at [hidden] (Supalov, Alexander) Date: Thu, 3 Apr 2008 09:28:08 +0100 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <20080403072551.GA15320@fourier.it.neclab.eu> Message-ID: <5ECAB1304A8B5B4CB3F9D6C01E4E21A2013390BC@swsmsx413.ger.corp.intel.com> Hi, Whatever the decision will be, we need it now. We're close to the point of no return for the September deadline. Best regards. Alexander -----Original Message----- From: Jesper Larsson Traeff [mailto:traff_at_it.neclab.eu] Sent: Thursday, April 03, 2008 9:26 AM To: Bronis R. de Supinski Cc: Supalov, Alexander; Rolf Rabenseifner; William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard Treumann; George Bosilca; David Solt; Rajeev Thakur; Jeff Squyres; MPI 2.1 Mailing List Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan Dear All, I agree with the comments of Bronis about datatypes - functionality that belongs together should be together in the STANDARD! (which is what we are writing). To me it seems that this 2.1 is somewhat more than the "merge" it was optimistically intended to be. Since this, as Bronis says, will likely be THE STANDARD for years to come, and the entry point for many new users, I think it is important that we get it right the first time, and I believe this is possible (if not, we should abort the attempt). It's good to have strict deadlines, but let's not be fanatical about that. I don't see any purpose whatsoever in putting out intermediate versions of 2.1 - as long as we are in limbo, 1.3 and 2.0 will work perfectly, they have all the ballots included I will try to send comments on/updates of my chapters (these will, I think/hope, not need so much) tomorrow/monday best regards Jesper On Wed, Apr 02, 2008 at 02:26:13PM -0700, Bronis R. de Supinski wrote: > > All: > > I thoroughly agree with the sentiment that many expressed > that we are better off slipping the release of 2.1 two or > four months more in order to get it right than hurrying to > get it out the door. It is likely to be THE standard for > a fairly long time and having it broken to begin with does > not seem wise. > > Bronis > > > On Wed, 2 Apr 2008, Supalov, Alexander wrote: > > > Hi, > > > > We may want to reduce the number of top level sections in the standard. > > In my opinion that I expressed to Rolf a couple of weeks ago, quite a > > few sections, like the ones mentioned by Bronis, should rather belong to > > a big Miscellany chapter rather than figure up there by themselves. They > > may also be merged/reformed, too. > > > > However, this is going to be a bigger change than envisioned originally. > > I wonder whether we should decide right away whether we can afford this > > now without slipping the planned MPI-2.1 delivery in September. A > > possible way would be to fix small things now and do second pass of > > major edits/reshuffling in MPI-3, or MPI-2.2, for that matter. > > > > Best regards. > > > > Alexander > > > > -----Original Message----- > > From: Bronis R. de Supinski [mailto:bronis_at_[hidden]] > > Sent: Wednesday, April 02, 2008 11:15 PM > > To: Rolf Rabenseifner > > Cc: William Gropp; Tony Skjellum; Rich Graham; Adam Moody; Richard > > Treumann; Jespar Larsson Traeff; George Bosilca; David Solt; Rajeev > > Thakur; Jeff Squyres; Supalov, Alexander; MPI 2.1 Mailing List > > Subject: Re: TODO - AUTHORS of MPI-2.1 - Workplan > > > > > > > > Rolf: > > > > I have not gone through Chapter 11 thoroughly yet but I have > > already noticed some major changes that I would suggest. > > > > First Section 11.6: "Decoding a Datatype" seems out of place > > in the merged document. It would make sense to me to have all > > of the datatype functions together. If we don't make datatypes > > a separate chapter, then this section (11.6) should be moved > > into chapter 3, near section 3.12: "Derived Datatypes". Ideally, > > it would be merged into that section since it is clearly part > > of that functionality. > > > > Second, Section 11.5: "Error Classes, Error Codes, and Error > > Handlers" is strongly related to Section 7.3: "Error Handling", > > and Section 7.4: "Error Codes and Classes". Clearly, these > > sections should be merged. In fact, this overlap makes me ask > > why have we not merged Chapters 7 and 11? What is the difference > > between "Environmental Management" and "External Interfaces"? > > > > I think this question needs to be resolved before I go further > > on working on Chapter 11. Perhaps George and I should coordinate > > merging these chapters after I coordinate moving the datatype > > decoding functionality into chapter 3 with Rich... > > > > Bronis > > > > > > > > > > On Wed, 2 Apr 2008, Bronis R. de Supinski wrote: > > > > > > > > Rolf: > > > > > > I have finished editing chapter 14: Profiling. I have > > > attached the modified prof.tex since I do not yet have > > > write access. More importantly, either there is a problem > > > with the 2.1 macros or I am doing something wrong (I think > > > it is the first but I am not LaTex fluent enough to be > > > certain). Specifically, the first letter of the word > > > following the end markers does not appear in the generated > > > PDF. I would appreciate it if you could look into which it is. > > > > > > Another observation is that the macro does not work around > > > empty sections. In particular, I tried to mark the section > > > that I moved with the macros, with the original text commented > > > out. I tried to do the same for some MPI-1.0 text that was > > > contradictory to or redundant with the text that I moved. > > > Having those empty macro regions caused the compile to fail. > > > It might be nice to have some way to flag the deleted text, > > > with the convention, at least for now, of just commenting > > > it out and not to delete it entirely from the file. > > > > > > Let me know if I am doing things right here and then I will > > > move on to fixing chapter 11: External Interfaces. Thanks, > > > > > > Bronis > > > > > > > > > On Wed, 2 Apr 2008, Rolf Rabenseifner wrote: > > > > > > > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > > > > Rajeev, Jeff, and Alexander, > > > > > > > > you are responsible for one ore more chapters of MPI-2.1 until the > > > > meeting. > > > > > > > > It is a tough schedule: > > > > ----------------------- > > > > > > > > * Tues, April 1, my ROUND ONE is finished and the write token is > > > > logically passed to all chapter authors: > > > > - You have read access to the source (via SVN) and the > > pdf. > > > > - You have write access to your local SVN copy. > > > > - You will get write access to the SVN in a few days. > > > > * Fri., April 11, chapter authors have finished ROUND TWO. > > > > - This is a hard deadline (because I've to go on travel) > > > > * Sat., April 12, I will produce mpi-report.pdf as basis for review > > > > (I cannot do later, because April 14-17, I'm on travel) > > > > * Mon.-Thu., April 14-17, strong review by the reviewer group > > > > * Fri., April 18, reviews - if necessary must be included - > > > > by the chapter authors > > > > * Sat., April 19, I will produce final mpi-report.pdf > > > > which is basis for > > > > - final reviews through the reviewer group > > > > - official reading at the April 28-30, 2008 meeting. > > > > (I cannot do later because I'm on travel April 20-26) > > > > > > > > The goals of your work as chapter author: > > > > ----------------------------------------- > > > > > > > > - Remove references to MPI-1 and MPI-2. > > > > - Substitute by MPI. > > > > - Necessary modifications to achieve this goal. > > > > > > > > With this, we should have a single MPI-2.1 standard that does > > > > not "know" the MPI-1 or MPI-2 history of individual functions. > > > > > > > > ** This should be mainly a task in the area of > > chapter-introductions. > > > > ** Please, never change the wording of function definitions. > > > > > > > > Exceptions: > > > > - There are routines that are deprecated and that are > > > > already referenced in a consistent way. > > > > My recommendation: > > > > Current wording: > > > > There are *new* function, and existing are now deprecated. > > > > Proposal: > > > > There are functions, and there exist also deprecated functions > > > > with (nearly) same functionality but deprecated due to some > > lack > > > > in the bindings (or functionality) > > > > - There is history information in the frontmatter. > > > > - there is a change-log annex with limited memory (only previous > > version) > > > > > > > > Technical editing rule: > > > > ----------------------- > > > > > > > > You must identify all of your changes: > > > > > > > > a) new/modified wording - you are highlighting your new/modified > > wording with: > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > modification > > > > .... your modified / new wording .... > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of > > modification > > > > > > > > b) Moved paragraphs, sentences, ... - you are highlighting the first > > word > > > > of the moved text with: > > > > > > > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of > > text-move > > > > First-word > > > > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing > > text-move > > > > ... rest of the moved text.... > > > > % MPI-2.1 round-two - end of text-move > > > > > > > > Caution: These macros work only in black parts of the text. > > > > > > > > In blue parts you must substitute > > > > \mpiiidotiMergeNEWforSINGLEendI% > > > > by > > > > \mpiiidotiMergeNEWforSINGLEendII% > > > > > > > > The highlighting is done with red color. > > > > (There are only a few other sentences from me magenta. > > > > Therefore red should be the best to highlight the round-two > > modifications.) > > > > > > > > Rsponsibilities: > > > > ---------------- > > > > > > > > * Frontmatter mpi-report.tex Bill Gropp > > > > * Acknowledgements credits.tex Rich Graham(text) + > > Rolf(emails-auth.) > > > > * 1. Introduction intro.tex Bill Gropp > > > > - 2. Terms terms-2.tex Tony Skjellum > > > > * 3. Point-to-point pt2pt.tex Rich Graham > > > > * 4. Collectives coll.tex Adam Moody > > > > * 5. Groups, etc. context.tex Dick Treumann > > > > - 6. Toplogies topol.tex Jesper Traeff > > > > * 7. Environment inquiry.tex George Bosilca > > > > - 8. Miscellany misc-2.tex Jesper Traeff > > > > - 9. Process Crea... dynamic-2.tex David Solt > > > > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > > > > - 11. External Int. ei-2.tex Bronis de Supinski > > > > - 12. IO io-2.tex Rajeev Thakur > > > > - 13. Lang.Binding binding-2.tex Jeff Squyres > > > > - 14. Profiling prof.tex Bronis de Supinski > > > > - 15. Deprecated deprecated.tex Rolf Rabenseifner > > > > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > > > > - Annex B Change-log changes.tex Rolf Rabenseifner > > > > - Bibliography refs.bib Bill Gropp > > > > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > > > > > > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > > > > only small work expected > > > > * There was a significant merge, or new text, or ..., > > > > more work expected > > > > > > > > I wish you a good start and good luck with your chapter. > > > > > > > > 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) > > > > > > --------------------------------------------------------------------- > > Intel GmbH > > Dornacher Strasse 1 > > 85622 Feldkirchen/Muenchen Germany > > Sitz der Gesellschaft: Feldkirchen bei Muenchen > > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > > VAT Registration No.: DE129385895 > > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > > > This e-mail and any attachments may contain confidential material for > > the sole use of the intended recipient(s). Any review or distribution > > by others is strictly prohibited. If you are not the intended > > recipient, please contact the sender and delete all copies. > > > > --------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen Germany Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr. VAT Registration No.: DE129385895 Citibank Frankfurt (BLZ 502 109 00) 600119052 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. From traff at [hidden] Fri Apr 4 10:31:19 2008 From: traff at [hidden] (Jesper Larsson Traeff) Date: Fri, 4 Apr 2008 17:31:19 +0200 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <20080404153119.GA3628@fourier.it.neclab.eu> Hallo Rolf, ich habe mit svn die sourcen geholt, soweit funktioniert alles. meine kapitel sind ja nicht gross, und auch nicht schweirig. Ich werde versuchen montag/dienstag fertig zu werden Eine bitte: mein nachnamen ist (in LaTeX): Tr\"aff - kannst du das in den acks a"ndern? Scho"nes wochenende Jesper On Wed, Apr 02, 2008 at 06:25:45PM +0200, Rolf Rabenseifner wrote: > Dear Bill, Tony, Rich, Adam, Dick, Jesper, George, David, Bronis, > Rajeev, Jeff, and Alexander, > > you are responsible for one ore more chapters of MPI-2.1 until the > meeting. > > It is a tough schedule: > ----------------------- > > * Tues, April 1, my ROUND ONE is finished and the write token is > logically passed to all chapter authors: > - You have read access to the source (via SVN) and the pdf. > - You have write access to your local SVN copy. > - You will get write access to the SVN in a few days. > * Fri., April 11, chapter authors have finished ROUND TWO. > - This is a hard deadline (because I've to go on travel) > * Sat., April 12, I will produce mpi-report.pdf as basis for review > (I cannot do later, because April 14-17, I'm on travel) > * Mon.-Thu., April 14-17, strong review by the reviewer group > * Fri., April 18, reviews - if necessary must be included - > by the chapter authors > * Sat., April 19, I will produce final mpi-report.pdf > which is basis for > - final reviews through the reviewer group > - official reading at the April 28-30, 2008 meeting. > (I cannot do later because I'm on travel April 20-26) > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > Rsponsibilities: > ---------------- > > * Frontmatter mpi-report.tex Bill Gropp > * Acknowledgements credits.tex Rich Graham(text) + Rolf(emails-auth.) > * 1. Introduction intro.tex Bill Gropp > - 2. Terms terms-2.tex Tony Skjellum > * 3. Point-to-point pt2pt.tex Rich Graham > * 4. Collectives coll.tex Adam Moody > * 5. Groups, etc. context.tex Dick Treumann > - 6. Toplogies topol.tex Jesper Traeff > * 7. Environment inquiry.tex George Bosilca > - 8. Miscellany misc-2.tex Jesper Traeff > - 9. Process Crea... dynamic-2.tex David Solt > - 10. One-sided Comm one-sided-2.tex Jepser Traeff > - 11. External Int. ei-2.tex Bronis de Supinski > - 12. IO io-2.tex Rajeev Thakur > - 13. Lang.Binding binding-2.tex Jeff Squyres > - 14. Profiling prof.tex Bronis de Supinski > - 15. Deprecated deprecated.tex Rolf Rabenseifner > - Annex A Lang.Bind. appLang*.tex, MAKE-APPLANG Alexander Supalov > - Annex B Change-log changes.tex Rolf Rabenseifner > - Bibliography refs.bib Bill Gropp > - Index MAKE-FUNC-INDEX Rolf Rabenseifner > > Legende: - Chapter is mainly taken from MPI-1.1 or MPI-2.0, > only small work expected > * There was a significant merge, or new text, or ..., > more work expected > > I wish you a good start and good luck with your chapter. > > 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) * -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2180 bytes Desc: smime.p7s URL: From treumann at [hidden] Mon Apr 7 09:54:00 2008 From: treumann at [hidden] (Richard Treumann) Date: Mon, 7 Apr 2008 10:54:00 -0400 Subject: [Mpi-21] 2.1 cleanup or MPI 2.2? Message-ID: In the description of MPI_COMM_FREE we presently give the following advise to implementors. A reference-count mechanism may be used: the reference count is incremented by each call to \func{MPI\_COMM\_DUP}, and decremented by each call to \func{MPI\_COMM\_FREE}. The object is ultimately deallocated when the count reaches zero. I do not think it can ever be valid to implement MPI_COMM_DUP by simply returning a new handle for an existing communicator object while bumping its reference count because the output communicator must have a different context than the original. Assuming I have not missed something, it seems this advise is nonsense. Is removing this the kind of change that should go on the MPI 2.2 list? I will be surprised if anyone offers a rationale for keeping the advise but I am also not quite comfortable that it fits within the "clean up" rules for MPI 2.1 at this late stage. Thoughts? Dick 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 * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsquyres at [hidden] Mon Apr 7 13:05:28 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 11:05:28 -0700 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <912EDC49-878B-4971-91BE-A172020AE0D2@cisco.com> The problem is that the text about language bindings is fairly disjoint between chapters 2 and 13. Indeed, chapter 13 is redundant and out of order / inconsistent with regards to MPI-1 text in some places *because* MPI-2 was a separate document. What about a slightly different proposal: 1. Move some of the existing Chapter 13/Language Bindings text into the relevant parts in the rest of the 2.1 doc (e.g., move the C++ communicators discussion to the Right place in Chapter 5/Groups, Contexts, Comms). 2. Make a new chapter 3: Language Bindings. Put in it: - All C/Fortran language bindings text from Chapter 2/Terms&Conv - All remaining text from Chapter 13/Language bindings 3. Remove the [now empty] Chapter 13 On Apr 4, 2008, at 7:48 AM, Rolf Rabenseifner wrote: > About Chap. 13, especially C++. > > I'm proposing (referencec to MPI-2.1 Draft Apr.1, 2008): > > - The MPI-2 Forum decided to put only small overview stuff into > Chap. 2 Terms. > (I want to recall, that in MPI-2 the Terms are rewritten for whole > MPI, > i.e., still valid in MPI-2.1) > - The MPI-2 Forum decided to put all deeper information into > extra sections of an additionally last chapter on Bindings. > - The MPI-2 Forum already decided that normal C++ bindings > should be after the Fortran bindings. > > - Terms, page 18, lines 36-39 clearly expresses, that all constants > are > given only in MPI_ notation and that C++ names (with MPI::) > are given in Annex A. > I.e., MPI_COMM_WORLD, MPI_FLOAT, MPI_PROC_NULL, ... should not > to be translated everywhere in the chapters. > Same for Table 3.2 on page 27. > > - There are important things were C++ clearly differs from C, > e.g. the handling of the Status. > I have already added the Status handling, see page 31 lines 23-32. > (By the way, this information was missing in Chap. 13.1 and only > available in the Annex A.) > > - I'm not aware, whether there are more such stuff, that is explained > for C and Fortran and should be also explained for C++. > Do you see an additional stuff like status? > > - I do not expect that it would be a good idee to move all the ugly > Fortran problems (17 pages) to the beginning of thee book into > Chap. 2 Terms. > I would recommend same rule for C++ (12 pages). > Chap.2 terms has only 16 pages - with 2 pages dedicated to Fortran, > 1/2 page to C, and 3 pages to C++. > > Best regards > Rolf > > On Thu, 3 Apr 2008 15:13:10 -0400 > Jeff Squyres wrote: >> On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: > ... >>> For me, the answer may have implications on how separate or >>> integrated additional bindings should be integrated into the >>> language independent text of the MPI standard. >> >> I don't quite understand. All officially-supported language bindings >> should be listed consistently in the standard. In MPI-2.1, for >> example, that means alongside the language neutral bindings in the >> text and in Annex A. > > > ------------- > > On Thu, 3 Apr 2008 15:27:08 -0400 > Jeff Squyres wrote: >> What about the C++/Fortran language bindings text? Should the >> majority of chapter 13 be merged into Terms and Conventions (and >> elsewhere)? >> >> It's not really a "problem", per se -- but it is a little awkward. >> There are sections in chapter 13 that could definitely fit in >> existing >> text elsewhere. Some of it is redundant, too. >> >> >> >> On Apr 3, 2008, at 3:19 PM, George Bosilca wrote: >>> Bronis, >>> >>> If the data-type section get moved into the chapter 3 it make sense >>> to merge the leftover of the chapter 11 with chapter 7, as long as >>> we choose a right name. "MPI Environmental Management" is not the >>> right chapter for "Generalized Requests". But of course these are >>> just details. >>> >>> I'll get in touch with you asap to see how we can coordinate. >>> >>> Thanks, >>> george. >>> >>> On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: >>>> >>>> Rolf: >>>> >>>> Re: >>>>> my general statements do not answer you initial question: >>>> >>>> My opinion is that leaving obvious problems unfixed based >>>> on an expected future version is a bad idea. However, I >>>> don't want to argue over this since I think the best >>>> approach is just to remove them now and then we don't >>>> have to worry about them. Others have more concerns over >>>> the time that they can devote to this (not that I have an >>>> abundance) and might want to delay in any event in order >>>> to get it right (at least mostly). >>>> >>>>> If you decide to move parts from Chap.11 to Chap.7, >>>>> then you both mus discuss this. You both are responsible >>>>> for these chapters. >>>>> And you should first convince your reviewers: >>>>> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill >>>>> - Chap.11: Bill and Rainer >>>>> My recommendation: >>>>> Express clearly which parts should be moved exactly to wich line >>>>> (all based on page/line numbers as **printed** in Draft Apr. 1, >>>>> 2008). >>>> >>>> I have discussed moving the datatype decoding stuff >>>> with Rich and Bill. I will move those sections as I >>>> suggested, with an initial pass for the current review. >>>> This works well for Rich since he does not have time >>>> to do this for another couple of weeks. I hope to get >>>> that done today. >>>> >>>> For the remainder, I will look over the two chapters >>>> (7 & 11) and propose an initial merge strategy. George >>>> can react to that; I don't know how long it will take >>>> me to get that done... >>>> >>>> Bronis >>>> >>>> _______________________________________________ >>>> 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 >> >> >> -- >> Jeff Squyres >> Cisco Systems >> >> _______________________________________________ >> mpi-21 mailing list >> mpi-21_at_[hidden] >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > > > 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 -- Jeff Squyres Cisco Systems From rabenseifner at [hidden] Mon Apr 7 13:18:04 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Mon, 07 Apr 2008 20:18:04 +0200 Subject: [Mpi-21] [Mpi-22] 2.1 cleanup or MPI 2.2? In-Reply-To: Message-ID: Dick, if I'm right, then 23.r is not similar. 23.r OK p183, lines 5-8. This advice to implementors on reference counts for groups should include MPI_COMM_GROUP as a routine that increments the reference count. I've put yours as 29.a in http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt 23.r I made an OK, but for your 29.a I would recommend to go to MPI-2.2. Best regards Rolf On Mon, 7 Apr 2008 10:54:00 -0400 Richard Treumann wrote: > > > In the description of MPI_COMM_FREE we presently give the following advise > to implementors. > > A reference-count mechanism may be used: the reference count is > incremented by each call to \func{MPI\_COMM\_DUP}, and decremented by > each call to \func{MPI\_COMM\_FREE}. The object is ultimately > deallocated when the count reaches zero. > > I do not think it can ever be valid to implement MPI_COMM_DUP by simply > returning a new handle for an existing communicator object while bumping > its reference count because the output communicator must have a different > context than the original. Assuming I have not missed something, it seems > this advise is nonsense. > > Is removing this the kind of change that should go on the MPI 2.2 list? I > will be surprised if anyone offers a rationale for keeping the advise but I > am also not quite comfortable that it fits within the "clean up" rules for > MPI 2.1 at this late stage. > > Thoughts? > > Dick > > > > 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 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) From jsquyres at [hidden] Mon Apr 7 13:18:32 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 11:18:32 -0700 Subject: [Mpi-21] MPI-2.1 April 1 document comments Message-ID: While reading the April 1 MPI-2.1 document for C++ and chapter 13 issues, I itemized a list of other issues that I found. Some may want to be pushed off to 2.2 (I have noted all of these with "--> This will require a vote") -- I leave these up to the Forum to decide -- but others should be fixed in 2.1. Enjoy. ----- April 7 2008 Comments on MPI-2.1 April 1, 2008 document (notation: pX.Y = page X, line Y) Overall ======= - Frontage numbering is still roman numerals -- I thought we agreed to have the physical and PDF page numbers agree. - Some function pointer typedefs are "_function", others are "_fn" We should be consistent throughout the text. Intro chapter ============= - p5.2: Two open source MPI implementations are cited that are no longer relevant. This entire sentence should be removed. Indeed, the language in the overall paragraph is forward-looking -- it should probably be re-worked to be in the present tense. - p6.46: Chapter 13 discusses Fortran issues (not Fortran 90 issues), and also discusses language interoperability issues. - p7.11: Looks like a broken LaTeX reference. Terms and Conventions ===================== - p9.40-10.10: The C and Fortran language neutral name do not include the prefix "MPI_", but the C++ bindings include the prefix "MPI::". Shouldn't the C/Fortran bindings be "MPI_CLASS_ACTION_SUBSET" (etc.)? - p10.35: due to the decision from last meeting (sort out the IN/OUT/INOUT mess in MPI-2.2), the language should be softened in this paragraph and the full paragraph following this one (because they contradict each other). Specifically, I propose changing: 10.35: Thus, in C++, IN aguments are either references... to Thus, in C++, IN arguments are usually either references... - p11.22: "Fortran in this document refers to Fortran 90". For MPI-2.1, it is probably suitable to leave this, but we might want to make a statement (footnote or parenthetical) that it is expected to be updated in future MPI spec revisions. Point-to-Point Communication ============================ - p66.33: Why is the request argument to the C bindings MPI_CANCEL take a pointer? The language neutral binding is IN, and the C++ binding is const. This seems to be a contradiction. --> This cannot be changed easily because every MPI implementation uses (MPI_Request *) as the type. - p83.29: extra space: "( int count," - p92.43: mising "const" before "void* location". Adding "const" will not break any user codes or MPI implementations. --> This will require a vote. - p95.47-48: remove "const" before lb an extent arguments. Removing "const" will not break any user codes or MPI implementations. --> This will require a vote. Collective Communications ========================= - p123.32: "relaxed" uses quote marks in the wrong direction - p123.27: should say "MPI-1" instead of "MPI-1.2" Groups, Contexts, and Communicators =================================== - p186.5: Descriptions for the C++ bindings need to be included here, since they are different than the C bindings. The text from 13.1.7 would seem to be sufficient. - p214.32: Missing "const" before "void* attribute_val_in" (datatype callback argument is const) --> This will require a vote. - p214.36: Delete function comm argument should be const (?) --> This will require a vote. - p219.5: Missing "const" before "void* attribute_val_in" (datatype callback argument is const) --> This will require a vote. - p219.9: Delete function win argument should be const (?) --> This will require a vote. - p221.44: Delete function type argument should be const (?) --> This will require a vote. MPI Environmental Management ============================ - p248.3: Earlier in the document, references are made to v1.3. Is that not a valid tuple to return from MPI_GET_VERSION? - p249.45: Remove duplicate C++ binding - p254.21: Remove erroneous MPI::Intracomm::Create C++ binding - p255.2: First argument (comm handle reference) to errhandler function should be const. --> This will require a vote. - p256.27: First argument (win handle reference) to errhandler function should be const. --> This will require a vote. - p257.41: First argument (file handle reference) to errhandler function should be const. --> This will require a vote. - p258.39: Delete duplicate C++ binding - p259.13: Delete duplicate C++ binding - p260.36-43: First letter of description should be capitolized to be consistent with rest of list. - p261.42: Delete duplicate C++ binding - p263.21-23: Delete duplicate C++ bindings - p264.22: Delete duplicate C++ binding - p267.24: Delete duplicate C++ binding - p267.42: Delete duplicate C++ binding Process Creation and Management =============================== - p288.11: Function should be const. --> This will require a vote. - p288.15: Function should be const. --> This will require a vote. External Interfaces =================== - p344.39: Arguments of query_fn, free_fn, and cancel_fn need to have *'s. This is a consistency issue (the rest of the standard uses "*" for function pointer parameters), not a correctness issue -- works both ways. Should not break any user code or MPI implementations. I/O === - p419.43: datatype argument should be const Language Bindings ================= - p437.18: Delete first sentence of paragraph - p437.22: Delete "original" - p437.24-29: Delete first and last sentences of paragraph - p437.29: New last sentence, "See Annex A.4.19 for a function cross reference." - p438.11: Delete "for MPI-1" - p438.14-37: Join the two namespaces together and delete the "Additionally, the following classes defined for MPI-2:" text. Re-sort the class names as appropriate. - p439.2: Delete last sentence ("To maintain ... in [23].") - p442: Table 13.1 is redundant with Annex A.1. However, the following C++ types are missing from Annex A.1: MPI::SIGNED_CHAR MPI::BOOL MPI::COMPLEX MPI::DOUBLE_COMPLEX MPI::LONG_DOUBLE_COMPLES - p442: Table 13.2 is redundant with Annex A.1 - p445.5-11: These functions are not listed in Annex A - p445.36-38: Remove this entire paragraph ("Compilers that do not support..."). This feature has been a part of C++ since C++98, and exists in all modern C++ compilers. - p446.7-17: Declarations for the MPI::Exceptions class are missing from Annex A - p448.47: Remove trailing "/" from "OUT/" - p450.26-44: The bullet list is wholly redundant with section 2.6.2. - p456.27-29: VOLATILE is in Fortran 200x; reword first sentence from: "In the longer term, the attribute VOLATILE is under consideration for Fortran 2000 and would give the buffer or variable the properties needed, but it would inhibit optimization of any code containing the buffer or variable." to "The VOLATILE attribute, available in later versions of Fortran, would give the buffer or variable the properties needed, but it would inhibit optimization of any code containing the buffer or variable." - p459.11-15: Delete paragraph - p462.43-45: Delete paragraph - p463.17-18: Delete first sentence; delete "In MPI-2," - p467.23: There is an extra space before "MPI_FINALIZE" - p468.16-39: None of these functions appear in Annex A (they should!) - p469.41 and 44: These functions do not appear in Annex A (they should!) - p470.46: Change sentence from: "It is important to note that all C++ objects and their corresponding C handles..." to "It is important to note that all C++ objects with corresponding C handles..." I.e., this sentence is referring only to C++ handles that actually have corresponding C handles (e.g., not MPI::ERRORS_THROW_EXCEPTIONS). Profiling Interface =================== - p481.4: Delete "const" --> This may require a vote. Annex A ======= - p494.15: s/Fortran/Fortran only - p494.30: Missing MPI::ERRORS_THROW_EXCEPTIONS - p495.18-19 and 33-34: MPI_BYTE and MPI_PACKED are listed in two separate tables. - p495.30: MPI::COMPLEX should be MPI::F_COMPLEX - p495.38: Looks like a blank extra 3rd column is in this table - p495.bottom: Missing table for "C++ only" datatypes: MPI::BOOL MPI::COMPLEX MPI::DOUBLE_COMPLEX MPI::LONG_DOUBLE_COMPLEX MPI::SIGNED_CHAR - p496.1: Add ", no Fortran" before the ")" - p496.10, s/Fortran/Fortran only/ - p496.27-30: Alignment of table entries should be to the left, not centered. - p544.13: Many of the prototypes for Clone() and Dup() are missing - p547.all: Many doubles of C++ bindings; likely because of errors in the chapter text. - p554.41: Do we need an empty deprecated functions section? - p555.45-46: Forgot to mention MPI_ERRCODES_IGNORE, MPI_F_STATUSES_IGNORE, and MPI_F_STATUS_IGNORE - p556.bottom: Missing prototypes for the MPI::Exceptions class -- Jeff Squyres Cisco Systems From bronis at [hidden] Mon Apr 7 13:22:47 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Mon, 7 Apr 2008 11:22:47 -0700 (PDT) Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: <912EDC49-878B-4971-91BE-A172020AE0D2@cisco.com> Message-ID: Jeff: I agree with most of your proposal. If stuff is wrong/outdated in Chapter 2, then it should be fixed. If stuff in Chapter 2 really belongs in a Language Bindings chapter, then it should be moved. However, I see no reason to make the language bindings chapter so early in the standard. In fact, I agree with Rolf's suggestion that it would be most appropriate as the last chapter, right before the appendix that lists the actual bindings. As Rolf suggested, we should make it chapter 14 and make the profiling interface chapter 13. Making it chapter 3 does not make sense. Bronis On Mon, 7 Apr 2008, Jeff Squyres wrote: > The problem is that the text about language bindings is fairly > disjoint between chapters 2 and 13. Indeed, chapter 13 is redundant > and out of order / inconsistent with regards to MPI-1 text in some > places *because* MPI-2 was a separate document. > > What about a slightly different proposal: > > 1. Move some of the existing Chapter 13/Language Bindings text into > the relevant parts in the rest of the 2.1 doc (e.g., move the C++ > communicators discussion to the Right place in Chapter 5/Groups, > Contexts, Comms). > > 2. Make a new chapter 3: Language Bindings. Put in it: > - All C/Fortran language bindings text from Chapter 2/Terms&Conv > - All remaining text from Chapter 13/Language bindings > > 3. Remove the [now empty] Chapter 13 > > > On Apr 4, 2008, at 7:48 AM, Rolf Rabenseifner wrote: > > About Chap. 13, especially C++. > > > > I'm proposing (referencec to MPI-2.1 Draft Apr.1, 2008): > > > > - The MPI-2 Forum decided to put only small overview stuff into > > Chap. 2 Terms. > > (I want to recall, that in MPI-2 the Terms are rewritten for whole > > MPI, > > i.e., still valid in MPI-2.1) > > - The MPI-2 Forum decided to put all deeper information into > > extra sections of an additionally last chapter on Bindings. > > - The MPI-2 Forum already decided that normal C++ bindings > > should be after the Fortran bindings. > > > > - Terms, page 18, lines 36-39 clearly expresses, that all constants > > are > > given only in MPI_ notation and that C++ names (with MPI::) > > are given in Annex A. > > I.e., MPI_COMM_WORLD, MPI_FLOAT, MPI_PROC_NULL, ... should not > > to be translated everywhere in the chapters. > > Same for Table 3.2 on page 27. > > > > - There are important things were C++ clearly differs from C, > > e.g. the handling of the Status. > > I have already added the Status handling, see page 31 lines 23-32. > > (By the way, this information was missing in Chap. 13.1 and only > > available in the Annex A.) > > > > - I'm not aware, whether there are more such stuff, that is explained > > for C and Fortran and should be also explained for C++. > > Do you see an additional stuff like status? > > > > - I do not expect that it would be a good idee to move all the ugly > > Fortran problems (17 pages) to the beginning of thee book into > > Chap. 2 Terms. > > I would recommend same rule for C++ (12 pages). > > Chap.2 terms has only 16 pages - with 2 pages dedicated to Fortran, > > 1/2 page to C, and 3 pages to C++. > > > > Best regards > > Rolf > > > > On Thu, 3 Apr 2008 15:13:10 -0400 > > Jeff Squyres wrote: > >> On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: > > ... > >>> For me, the answer may have implications on how separate or > >>> integrated additional bindings should be integrated into the > >>> language independent text of the MPI standard. > >> > >> I don't quite understand. All officially-supported language bindings > >> should be listed consistently in the standard. In MPI-2.1, for > >> example, that means alongside the language neutral bindings in the > >> text and in Annex A. > > > > > > ------------- > > > > On Thu, 3 Apr 2008 15:27:08 -0400 > > Jeff Squyres wrote: > >> What about the C++/Fortran language bindings text? Should the > >> majority of chapter 13 be merged into Terms and Conventions (and > >> elsewhere)? > >> > >> It's not really a "problem", per se -- but it is a little awkward. > >> There are sections in chapter 13 that could definitely fit in > >> existing > >> text elsewhere. Some of it is redundant, too. > >> > >> > >> > >> On Apr 3, 2008, at 3:19 PM, George Bosilca wrote: > >>> Bronis, > >>> > >>> If the data-type section get moved into the chapter 3 it make sense > >>> to merge the leftover of the chapter 11 with chapter 7, as long as > >>> we choose a right name. "MPI Environmental Management" is not the > >>> right chapter for "Generalized Requests". But of course these are > >>> just details. > >>> > >>> I'll get in touch with you asap to see how we can coordinate. > >>> > >>> Thanks, > >>> george. > >>> > >>> On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: > >>>> > >>>> Rolf: > >>>> > >>>> Re: > >>>>> my general statements do not answer you initial question: > >>>> > >>>> My opinion is that leaving obvious problems unfixed based > >>>> on an expected future version is a bad idea. However, I > >>>> don't want to argue over this since I think the best > >>>> approach is just to remove them now and then we don't > >>>> have to worry about them. Others have more concerns over > >>>> the time that they can devote to this (not that I have an > >>>> abundance) and might want to delay in any event in order > >>>> to get it right (at least mostly). > >>>> > >>>>> If you decide to move parts from Chap.11 to Chap.7, > >>>>> then you both mus discuss this. You both are responsible > >>>>> for these chapters. > >>>>> And you should first convince your reviewers: > >>>>> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill > >>>>> - Chap.11: Bill and Rainer > >>>>> My recommendation: > >>>>> Express clearly which parts should be moved exactly to wich line > >>>>> (all based on page/line numbers as **printed** in Draft Apr. 1, > >>>>> 2008). > >>>> > >>>> I have discussed moving the datatype decoding stuff > >>>> with Rich and Bill. I will move those sections as I > >>>> suggested, with an initial pass for the current review. > >>>> This works well for Rich since he does not have time > >>>> to do this for another couple of weeks. I hope to get > >>>> that done today. > >>>> > >>>> For the remainder, I will look over the two chapters > >>>> (7 & 11) and propose an initial merge strategy. George > >>>> can react to that; I don't know how long it will take > >>>> me to get that done... > >>>> > >>>> Bronis > >>>> > >>>> _______________________________________________ > >>>> 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 > >> > >> > >> -- > >> Jeff Squyres > >> Cisco Systems > >> > >> _______________________________________________ > >> mpi-21 mailing list > >> mpi-21_at_[hidden] > >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > > > > > > > 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 > > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > From bronis at [hidden] Mon Apr 7 13:29:30 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Mon, 7 Apr 2008 11:29:30 -0700 (PDT) Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: Jeff: The PDF and physical page numbers do agree. That does not require numbering the frontage material from 1. When I view page xvi, my PDF reader says "xvi (16 of 603)". Perhaps your reader is broken? Bronis On Mon, 7 Apr 2008, Jeff Squyres wrote: > While reading the April 1 MPI-2.1 document for C++ and chapter 13 > issues, I itemized a list of other issues that I found. Some may want > to be pushed off to 2.2 (I have noted all of these with "--> This will > require a vote") -- I leave these up to the Forum to decide -- but > others should be fixed in 2.1. > > Enjoy. > > ----- > > April 7 2008 > Comments on MPI-2.1 April 1, 2008 document > > (notation: pX.Y = page X, line Y) > > Overall > ======= > > - Frontage numbering is still roman numerals -- I thought we agreed to > have the physical and PDF page numbers agree. > > - Some function pointer typedefs are "_function", others are "_fn" > We should be consistent throughout the text. > > Intro chapter > ============= > > - p5.2: Two open source MPI implementations are cited that are no > longer relevant. This entire sentence should be removed. Indeed, > the language in the overall paragraph is forward-looking -- it > should probably be re-worked to be in the present tense. > > - p6.46: Chapter 13 discusses Fortran issues (not Fortran 90 issues), > and also discusses language interoperability issues. > > - p7.11: Looks like a broken LaTeX reference. > > Terms and Conventions > ===================== > > - p9.40-10.10: The C and Fortran language neutral name do not include > the prefix "MPI_", but the C++ bindings include the prefix "MPI::". > Shouldn't the C/Fortran bindings be "MPI_CLASS_ACTION_SUBSET" > (etc.)? > > - p10.35: due to the decision from last meeting (sort out the > IN/OUT/INOUT mess in MPI-2.2), the language should be softened in > this paragraph and the full paragraph following this one (because > they contradict each other). Specifically, I propose changing: > > 10.35: Thus, in C++, IN aguments are either references... > to > Thus, in C++, IN arguments are usually either references... > > - p11.22: "Fortran in this document refers to Fortran 90". For > MPI-2.1, it is probably suitable to leave this, but we might want to > make a statement (footnote or parenthetical) that it is expected to > be updated in future MPI spec revisions. > > > Point-to-Point Communication > ============================ > > - p66.33: Why is the request argument to the C bindings MPI_CANCEL > take a pointer? The language neutral binding is IN, and the C++ > binding is const. This seems to be a contradiction. > --> This cannot be changed easily because every MPI implementation > uses (MPI_Request *) as the type. > > - p83.29: extra space: "( int count," > > - p92.43: mising "const" before "void* location". Adding "const" > will not break any user codes or MPI implementations. > --> This will require a vote. > > - p95.47-48: remove "const" before lb an extent arguments. > Removing "const" will not break any user codes or MPI > implementations. > --> This will require a vote. > > Collective Communications > ========================= > > - p123.32: "relaxed" uses quote marks in the wrong direction > > - p123.27: should say "MPI-1" instead of "MPI-1.2" > > Groups, Contexts, and Communicators > =================================== > > - p186.5: Descriptions for the C++ bindings need to be included here, > since they are different than the C bindings. The text from 13.1.7 > would seem to be sufficient. > > - p214.32: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p214.36: Delete function comm argument should be const (?) > --> This will require a vote. > > - p219.5: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p219.9: Delete function win argument should be const (?) > --> This will require a vote. > > - p221.44: Delete function type argument should be const (?) > --> This will require a vote. > > MPI Environmental Management > ============================ > > - p248.3: Earlier in the document, references are made to v1.3. Is > that not a valid tuple to return from MPI_GET_VERSION? > > - p249.45: Remove duplicate C++ binding > > - p254.21: Remove erroneous MPI::Intracomm::Create C++ binding > > - p255.2: First argument (comm handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p256.27: First argument (win handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p257.41: First argument (file handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p258.39: Delete duplicate C++ binding > > - p259.13: Delete duplicate C++ binding > > - p260.36-43: First letter of description should be capitolized to be > consistent with rest of list. > > - p261.42: Delete duplicate C++ binding > > - p263.21-23: Delete duplicate C++ bindings > > - p264.22: Delete duplicate C++ binding > > - p267.24: Delete duplicate C++ binding > > - p267.42: Delete duplicate C++ binding > > Process Creation and Management > =============================== > > - p288.11: Function should be const. > --> This will require a vote. > > - p288.15: Function should be const. > --> This will require a vote. > > External Interfaces > =================== > > - p344.39: Arguments of query_fn, free_fn, and cancel_fn need to have > *'s. This is a consistency issue (the rest of the standard uses > "*" for function pointer parameters), not a correctness issue -- > works both ways. Should not break any user code or MPI > implementations. > > I/O > === > > - p419.43: datatype argument should be const > > Language Bindings > ================= > > - p437.18: Delete first sentence of paragraph > > - p437.22: Delete "original" > > - p437.24-29: Delete first and last sentences of paragraph > > - p437.29: New last sentence, "See Annex A.4.19 for a function cross > reference." > > - p438.11: Delete "for MPI-1" > > - p438.14-37: Join the two namespaces together and delete the > "Additionally, the following classes defined for MPI-2:" text. > Re-sort the class names as appropriate. > > - p439.2: Delete last sentence ("To maintain ... in [23].") > > - p442: Table 13.1 is redundant with Annex A.1. However, the > following C++ types are missing from Annex A.1: > > MPI::SIGNED_CHAR > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLES > > - p442: Table 13.2 is redundant with Annex A.1 > > - p445.5-11: These functions are not listed in Annex A > > - p445.36-38: Remove this entire paragraph ("Compilers that do not > support..."). This feature has been a part of C++ since C++98, and > exists in all modern C++ compilers. > > - p446.7-17: Declarations for the MPI::Exceptions class are missing > from Annex A > > - p448.47: Remove trailing "/" from "OUT/" > > - p450.26-44: The bullet list is wholly redundant with section 2.6.2. > > - p456.27-29: VOLATILE is in Fortran 200x; reword first sentence from: > "In the longer term, the attribute VOLATILE is under > consideration for Fortran 2000 and would give the buffer or > variable the properties needed, but it would inhibit > optimization of any code containing the buffer or variable." > to > "The VOLATILE attribute, available in later versions of Fortran, > would give the buffer or variable the properties needed, but it > would inhibit optimization of any code containing the buffer or > variable." > > - p459.11-15: Delete paragraph > > - p462.43-45: Delete paragraph > > - p463.17-18: Delete first sentence; delete "In MPI-2," > > - p467.23: There is an extra space before "MPI_FINALIZE" > > - p468.16-39: None of these functions appear in Annex A (they > should!) > > - p469.41 and 44: These functions do not appear in Annex A (they > should!) > > - p470.46: Change sentence from: > "It is important to note that all C++ objects and their > corresponding C handles..." > to > "It is important to note that all C++ objects with > corresponding C handles..." > I.e., this sentence is referring only to C++ handles that actually > have corresponding C handles (e.g., not > MPI::ERRORS_THROW_EXCEPTIONS). > > Profiling Interface > =================== > > - p481.4: Delete "const" > --> This may require a vote. > > Annex A > ======= > > - p494.15: s/Fortran/Fortran only > > - p494.30: Missing MPI::ERRORS_THROW_EXCEPTIONS > > - p495.18-19 and 33-34: MPI_BYTE and MPI_PACKED are listed in two > separate tables. > > - p495.30: MPI::COMPLEX should be MPI::F_COMPLEX > > - p495.38: Looks like a blank extra 3rd column is in this table > > - p495.bottom: Missing table for "C++ only" datatypes: > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLEX > MPI::SIGNED_CHAR > > - p496.1: Add ", no Fortran" before the ")" > > - p496.10, s/Fortran/Fortran only/ > > - p496.27-30: Alignment of table entries should be to the left, not > centered. > > - p544.13: Many of the prototypes for Clone() and Dup() are missing > > - p547.all: Many doubles of C++ bindings; likely because of errors in > the chapter text. > > - p554.41: Do we need an empty deprecated functions section? > > - p555.45-46: Forgot to mention MPI_ERRCODES_IGNORE, > MPI_F_STATUSES_IGNORE, and MPI_F_STATUS_IGNORE > > - p556.bottom: Missing prototypes for the MPI::Exceptions class > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > From bronis at [hidden] Mon Apr 7 13:32:40 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Mon, 7 Apr 2008 11:32:40 -0700 (PDT) Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: Jeff: You should send the individual issues to the chapter owners. I will try to look over the issues for chapters 11 and 14. I don't have a strong opinon on either of them and will certainly delete the "const" in chapter 14 if others agree. Bronis On Mon, 7 Apr 2008, Jeff Squyres wrote: > While reading the April 1 MPI-2.1 document for C++ and chapter 13 > issues, I itemized a list of other issues that I found. Some may want > to be pushed off to 2.2 (I have noted all of these with "--> This will > require a vote") -- I leave these up to the Forum to decide -- but > others should be fixed in 2.1. > > Enjoy. > > ----- > > April 7 2008 > Comments on MPI-2.1 April 1, 2008 document > > (notation: pX.Y = page X, line Y) > > Overall > ======= > > - Frontage numbering is still roman numerals -- I thought we agreed to > have the physical and PDF page numbers agree. > > - Some function pointer typedefs are "_function", others are "_fn" > We should be consistent throughout the text. > > Intro chapter > ============= > > - p5.2: Two open source MPI implementations are cited that are no > longer relevant. This entire sentence should be removed. Indeed, > the language in the overall paragraph is forward-looking -- it > should probably be re-worked to be in the present tense. > > - p6.46: Chapter 13 discusses Fortran issues (not Fortran 90 issues), > and also discusses language interoperability issues. > > - p7.11: Looks like a broken LaTeX reference. > > Terms and Conventions > ===================== > > - p9.40-10.10: The C and Fortran language neutral name do not include > the prefix "MPI_", but the C++ bindings include the prefix "MPI::". > Shouldn't the C/Fortran bindings be "MPI_CLASS_ACTION_SUBSET" > (etc.)? > > - p10.35: due to the decision from last meeting (sort out the > IN/OUT/INOUT mess in MPI-2.2), the language should be softened in > this paragraph and the full paragraph following this one (because > they contradict each other). Specifically, I propose changing: > > 10.35: Thus, in C++, IN aguments are either references... > to > Thus, in C++, IN arguments are usually either references... > > - p11.22: "Fortran in this document refers to Fortran 90". For > MPI-2.1, it is probably suitable to leave this, but we might want to > make a statement (footnote or parenthetical) that it is expected to > be updated in future MPI spec revisions. > > > Point-to-Point Communication > ============================ > > - p66.33: Why is the request argument to the C bindings MPI_CANCEL > take a pointer? The language neutral binding is IN, and the C++ > binding is const. This seems to be a contradiction. > --> This cannot be changed easily because every MPI implementation > uses (MPI_Request *) as the type. > > - p83.29: extra space: "( int count," > > - p92.43: mising "const" before "void* location". Adding "const" > will not break any user codes or MPI implementations. > --> This will require a vote. > > - p95.47-48: remove "const" before lb an extent arguments. > Removing "const" will not break any user codes or MPI > implementations. > --> This will require a vote. > > Collective Communications > ========================= > > - p123.32: "relaxed" uses quote marks in the wrong direction > > - p123.27: should say "MPI-1" instead of "MPI-1.2" > > Groups, Contexts, and Communicators > =================================== > > - p186.5: Descriptions for the C++ bindings need to be included here, > since they are different than the C bindings. The text from 13.1.7 > would seem to be sufficient. > > - p214.32: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p214.36: Delete function comm argument should be const (?) > --> This will require a vote. > > - p219.5: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p219.9: Delete function win argument should be const (?) > --> This will require a vote. > > - p221.44: Delete function type argument should be const (?) > --> This will require a vote. > > MPI Environmental Management > ============================ > > - p248.3: Earlier in the document, references are made to v1.3. Is > that not a valid tuple to return from MPI_GET_VERSION? > > - p249.45: Remove duplicate C++ binding > > - p254.21: Remove erroneous MPI::Intracomm::Create C++ binding > > - p255.2: First argument (comm handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p256.27: First argument (win handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p257.41: First argument (file handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p258.39: Delete duplicate C++ binding > > - p259.13: Delete duplicate C++ binding > > - p260.36-43: First letter of description should be capitolized to be > consistent with rest of list. > > - p261.42: Delete duplicate C++ binding > > - p263.21-23: Delete duplicate C++ bindings > > - p264.22: Delete duplicate C++ binding > > - p267.24: Delete duplicate C++ binding > > - p267.42: Delete duplicate C++ binding > > Process Creation and Management > =============================== > > - p288.11: Function should be const. > --> This will require a vote. > > - p288.15: Function should be const. > --> This will require a vote. > > External Interfaces > =================== > > - p344.39: Arguments of query_fn, free_fn, and cancel_fn need to have > *'s. This is a consistency issue (the rest of the standard uses > "*" for function pointer parameters), not a correctness issue -- > works both ways. Should not break any user code or MPI > implementations. > > I/O > === > > - p419.43: datatype argument should be const > > Language Bindings > ================= > > - p437.18: Delete first sentence of paragraph > > - p437.22: Delete "original" > > - p437.24-29: Delete first and last sentences of paragraph > > - p437.29: New last sentence, "See Annex A.4.19 for a function cross > reference." > > - p438.11: Delete "for MPI-1" > > - p438.14-37: Join the two namespaces together and delete the > "Additionally, the following classes defined for MPI-2:" text. > Re-sort the class names as appropriate. > > - p439.2: Delete last sentence ("To maintain ... in [23].") > > - p442: Table 13.1 is redundant with Annex A.1. However, the > following C++ types are missing from Annex A.1: > > MPI::SIGNED_CHAR > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLES > > - p442: Table 13.2 is redundant with Annex A.1 > > - p445.5-11: These functions are not listed in Annex A > > - p445.36-38: Remove this entire paragraph ("Compilers that do not > support..."). This feature has been a part of C++ since C++98, and > exists in all modern C++ compilers. > > - p446.7-17: Declarations for the MPI::Exceptions class are missing > from Annex A > > - p448.47: Remove trailing "/" from "OUT/" > > - p450.26-44: The bullet list is wholly redundant with section 2.6.2. > > - p456.27-29: VOLATILE is in Fortran 200x; reword first sentence from: > "In the longer term, the attribute VOLATILE is under > consideration for Fortran 2000 and would give the buffer or > variable the properties needed, but it would inhibit > optimization of any code containing the buffer or variable." > to > "The VOLATILE attribute, available in later versions of Fortran, > would give the buffer or variable the properties needed, but it > would inhibit optimization of any code containing the buffer or > variable." > > - p459.11-15: Delete paragraph > > - p462.43-45: Delete paragraph > > - p463.17-18: Delete first sentence; delete "In MPI-2," > > - p467.23: There is an extra space before "MPI_FINALIZE" > > - p468.16-39: None of these functions appear in Annex A (they > should!) > > - p469.41 and 44: These functions do not appear in Annex A (they > should!) > > - p470.46: Change sentence from: > "It is important to note that all C++ objects and their > corresponding C handles..." > to > "It is important to note that all C++ objects with > corresponding C handles..." > I.e., this sentence is referring only to C++ handles that actually > have corresponding C handles (e.g., not > MPI::ERRORS_THROW_EXCEPTIONS). > > Profiling Interface > =================== > > - p481.4: Delete "const" > --> This may require a vote. > > Annex A > ======= > > - p494.15: s/Fortran/Fortran only > > - p494.30: Missing MPI::ERRORS_THROW_EXCEPTIONS > > - p495.18-19 and 33-34: MPI_BYTE and MPI_PACKED are listed in two > separate tables. > > - p495.30: MPI::COMPLEX should be MPI::F_COMPLEX > > - p495.38: Looks like a blank extra 3rd column is in this table > > - p495.bottom: Missing table for "C++ only" datatypes: > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLEX > MPI::SIGNED_CHAR > > - p496.1: Add ", no Fortran" before the ")" > > - p496.10, s/Fortran/Fortran only/ > > - p496.27-30: Alignment of table entries should be to the left, not > centered. > > - p544.13: Many of the prototypes for Clone() and Dup() are missing > > - p547.all: Many doubles of C++ bindings; likely because of errors in > the chapter text. > > - p554.41: Do we need an empty deprecated functions section? > > - p555.45-46: Forgot to mention MPI_ERRCODES_IGNORE, > MPI_F_STATUSES_IGNORE, and MPI_F_STATUS_IGNORE > > - p556.bottom: Missing prototypes for the MPI::Exceptions class > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > From jsquyres at [hidden] Mon Apr 7 13:36:58 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 11:36:58 -0700 Subject: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan In-Reply-To: Message-ID: <981A9923-D476-4707-8E8B-EB0DDB9981FD@cisco.com> MPI-1 included the bindings issues / rationale information in an early chapter because it provides the basis behind the bindings presented in the rest of the document. I still think that that's a good idea (e.g., all of functions are MPI_, in C++ we have these basic classes, etc.). I think it would read pretty weird if you read the whole MPI-2.1 document and then in the last chapter you see "here's why all the bindings are the way that they are". That's why I proposed that this stuff be moved into a [new] chapter 3 -- keep the information at the beginning of the document, but it's now big enough to be its own chapter. My $0.02. :-) On Apr 7, 2008, at 11:22 AM, Bronis R. de Supinski wrote: > > Jeff: > > I agree with most of your proposal. > > If stuff is wrong/outdated in Chapter 2, then it should be fixed. > > If stuff in Chapter 2 really belongs in a Language Bindings chapter, > then it should be moved. > > However, I see no reason to make the language bindings chapter so > early in the standard. In fact, I agree with Rolf's suggestion > that it would be most appropriate as the last chapter, right > before the appendix that lists the actual bindings. As Rolf > suggested, we should make it chapter 14 and make the profiling > interface chapter 13. Making it chapter 3 does not make sense. > > Bronis > > > > On Mon, 7 Apr 2008, Jeff Squyres wrote: > >> The problem is that the text about language bindings is fairly >> disjoint between chapters 2 and 13. Indeed, chapter 13 is redundant >> and out of order / inconsistent with regards to MPI-1 text in some >> places *because* MPI-2 was a separate document. >> >> What about a slightly different proposal: >> >> 1. Move some of the existing Chapter 13/Language Bindings text into >> the relevant parts in the rest of the 2.1 doc (e.g., move the C++ >> communicators discussion to the Right place in Chapter 5/Groups, >> Contexts, Comms). >> >> 2. Make a new chapter 3: Language Bindings. Put in it: >> - All C/Fortran language bindings text from Chapter 2/Terms&Conv >> - All remaining text from Chapter 13/Language bindings >> >> 3. Remove the [now empty] Chapter 13 >> >> >> On Apr 4, 2008, at 7:48 AM, Rolf Rabenseifner wrote: >>> About Chap. 13, especially C++. >>> >>> I'm proposing (referencec to MPI-2.1 Draft Apr.1, 2008): >>> >>> - The MPI-2 Forum decided to put only small overview stuff into >>> Chap. 2 Terms. >>> (I want to recall, that in MPI-2 the Terms are rewritten for whole >>> MPI, >>> i.e., still valid in MPI-2.1) >>> - The MPI-2 Forum decided to put all deeper information into >>> extra sections of an additionally last chapter on Bindings. >>> - The MPI-2 Forum already decided that normal C++ bindings >>> should be after the Fortran bindings. >>> >>> - Terms, page 18, lines 36-39 clearly expresses, that all constants >>> are >>> given only in MPI_ notation and that C++ names (with MPI::) >>> are given in Annex A. >>> I.e., MPI_COMM_WORLD, MPI_FLOAT, MPI_PROC_NULL, ... should not >>> to be translated everywhere in the chapters. >>> Same for Table 3.2 on page 27. >>> >>> - There are important things were C++ clearly differs from C, >>> e.g. the handling of the Status. >>> I have already added the Status handling, see page 31 lines 23-32. >>> (By the way, this information was missing in Chap. 13.1 and only >>> available in the Annex A.) >>> >>> - I'm not aware, whether there are more such stuff, that is >>> explained >>> for C and Fortran and should be also explained for C++. >>> Do you see an additional stuff like status? >>> >>> - I do not expect that it would be a good idee to move all the ugly >>> Fortran problems (17 pages) to the beginning of thee book into >>> Chap. 2 Terms. >>> I would recommend same rule for C++ (12 pages). >>> Chap.2 terms has only 16 pages - with 2 pages dedicated to Fortran, >>> 1/2 page to C, and 3 pages to C++. >>> >>> Best regards >>> Rolf >>> >>> On Thu, 3 Apr 2008 15:13:10 -0400 >>> Jeff Squyres wrote: >>>> On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: >>> ... >>>>> For me, the answer may have implications on how separate or >>>>> integrated additional bindings should be integrated into the >>>>> language independent text of the MPI standard. >>>> >>>> I don't quite understand. All officially-supported language >>>> bindings >>>> should be listed consistently in the standard. In MPI-2.1, for >>>> example, that means alongside the language neutral bindings in the >>>> text and in Annex A. >>> >>> >>> ------------- >>> >>> On Thu, 3 Apr 2008 15:27:08 -0400 >>> Jeff Squyres wrote: >>>> What about the C++/Fortran language bindings text? Should the >>>> majority of chapter 13 be merged into Terms and Conventions (and >>>> elsewhere)? >>>> >>>> It's not really a "problem", per se -- but it is a little awkward. >>>> There are sections in chapter 13 that could definitely fit in >>>> existing >>>> text elsewhere. Some of it is redundant, too. >>>> >>>> >>>> >>>> On Apr 3, 2008, at 3:19 PM, George Bosilca wrote: >>>>> Bronis, >>>>> >>>>> If the data-type section get moved into the chapter 3 it make >>>>> sense >>>>> to merge the leftover of the chapter 11 with chapter 7, as long as >>>>> we choose a right name. "MPI Environmental Management" is not the >>>>> right chapter for "Generalized Requests". But of course these are >>>>> just details. >>>>> >>>>> I'll get in touch with you asap to see how we can coordinate. >>>>> >>>>> Thanks, >>>>> george. >>>>> >>>>> On Apr 3, 2008, at 12:58 PM, Bronis R. de Supinski wrote: >>>>>> >>>>>> Rolf: >>>>>> >>>>>> Re: >>>>>>> my general statements do not answer you initial question: >>>>>> >>>>>> My opinion is that leaving obvious problems unfixed based >>>>>> on an expected future version is a bad idea. However, I >>>>>> don't want to argue over this since I think the best >>>>>> approach is just to remove them now and then we don't >>>>>> have to worry about them. Others have more concerns over >>>>>> the time that they can devote to this (not that I have an >>>>>> abundance) and might want to delay in any event in order >>>>>> to get it right (at least mostly). >>>>>> >>>>>>> If you decide to move parts from Chap.11 to Chap.7, >>>>>>> then you both mus discuss this. You both are responsible >>>>>>> for these chapters. >>>>>>> And you should first convince your reviewers: >>>>>>> - Chap. 7: Rich, Jesper, Steve, Kannan, David, Bill >>>>>>> - Chap.11: Bill and Rainer >>>>>>> My recommendation: >>>>>>> Express clearly which parts should be moved exactly to wich line >>>>>>> (all based on page/line numbers as **printed** in Draft Apr. 1, >>>>>>> 2008). >>>>>> >>>>>> I have discussed moving the datatype decoding stuff >>>>>> with Rich and Bill. I will move those sections as I >>>>>> suggested, with an initial pass for the current review. >>>>>> This works well for Rich since he does not have time >>>>>> to do this for another couple of weeks. I hope to get >>>>>> that done today. >>>>>> >>>>>> For the remainder, I will look over the two chapters >>>>>> (7 & 11) and propose an initial merge strategy. George >>>>>> can react to that; I don't know how long it will take >>>>>> me to get that done... >>>>>> >>>>>> Bronis >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>>> -- >>>> Jeff Squyres >>>> Cisco Systems >>>> >>>> _______________________________________________ >>>> mpi-21 mailing list >>>> mpi-21_at_[hidden] >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 >>> >>> >>> >>> 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 >> >> >> -- >> Jeff Squyres >> Cisco Systems >> >> _______________________________________________ >> 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 -- Jeff Squyres Cisco Systems From gropp at [hidden] Mon Apr 7 13:37:20 2008 From: gropp at [hidden] (William Gropp) Date: Mon, 7 Apr 2008 13:37:20 -0500 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: <31670107-767B-42FC-B0FF-8C5071F34833@mcs.anl.gov> The numbers do agree - we changed the LaTeX options so that the PDF knows the real numbers, which include roman for front matter. It would be wrong to number the pages sequentially from 1, abandoning long-established practice with documents. And at least on a Mac, both Preview and Acrobat both display the correct page number and will goto that page (including going to "xi"). Before we fixed this, those display programs did not know how the pages were numbered, and just (incorrectly) counted forward from one. Now the document meets standard page numbering conventions, and the PDF display programs are aware of the true page numbers. Bill On Apr 7, 2008, at 1:18 PM, Jeff Squyres wrote: > Overall > ======= > > - Frontage numbering is still roman numerals -- I thought we agreed to > have the physical and PDF page numbers agree. > William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsquyres at [hidden] Mon Apr 7 13:39:32 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 11:39:32 -0700 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: On Apr 7, 2008, at 11:29 AM, Bronis R. de Supinski wrote: > > The PDF and physical page numbers do agree. That does not > require numbering the frontage material from 1. When I view > page xvi, my PDF reader says "xvi (16 of 603)". > > Perhaps your reader is broken? Perhaps it is; I'm using Preview in Mac/OS X 10.5.2. Does gv show the Roman numerals? -- Jeff Squyres Cisco Systems From jsquyres at [hidden] Mon Apr 7 13:41:56 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 11:41:56 -0700 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: On Apr 7, 2008, at 11:32 AM, Bronis R. de Supinski wrote: > > You should send the individual issues to the chapter owners. Aren't all of them on this list? :-) > I will try to look over the issues for chapters 11 and 14. > I don't have a strong opinon on either of them and will > certainly delete the "const" in chapter 14 if others agree. Thanks. -- Jeff Squyres Cisco Systems From jsquyres at [hidden] Mon Apr 7 14:07:28 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 7 Apr 2008 12:07:28 -0700 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: <31670107-767B-42FC-B0FF-8C5071F34833@mcs.anl.gov> Message-ID: <04151B37-4C87-48F4-8712-2B8D9D25AEEE@cisco.com> Ahh... I see. There's a non-default option in OS X Preview that you have to enable ("Use logical page numbers"), and then it all works fine. Thanks, Apple. ;-) Thanks! On Apr 7, 2008, at 11:37 AM, William Gropp wrote: > The numbers do agree - we changed the LaTeX options so that the PDF > knows the real numbers, which include roman for front matter. It > would be wrong to number the pages sequentially from 1, abandoning > long-established practice with documents. And at least on a Mac, > both Preview and Acrobat both display the correct page number and > will goto that page (including going to "xi"). Before we fixed > this, those display programs did not know how the pages were > numbered, and just (incorrectly) counted forward from one. Now the > document meets standard page numbering conventions, and the PDF > display programs are aware of the true page numbers. > > Bill > > On Apr 7, 2008, at 1:18 PM, Jeff Squyres wrote: >> Overall >> ======= >> >> - Frontage numbering is still roman numerals -- I thought we agreed >> to >> have the physical and PDF page numbers agree. >> > > William Gropp > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 -- Jeff Squyres Cisco Systems From rabenseifner at [hidden] Mon Apr 7 14:41:13 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Mon, 07 Apr 2008 21:41:13 +0200 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: <31670107-767B-42FC-B0FF-8C5071F34833@mcs.anl.gov> Message-ID: Yes it was 10.d on the long list. We keep roman for frontmatter. Now pdf has correct numbering (My acroread under Windows works really fine) (My acroread under Linux is a little bit ugly, it computes and shows also the global numbering :-( ) On Mon, 7 Apr 2008 13:37:20 -0500 William Gropp wrote: > The numbers do agree - we changed the LaTeX options so that the PDF knows the real numbers, which include roman for front matter. It would be wrong to number the pages sequentially from 1, abandoning long-established practice with documents. And at least on a Mac, both Preview and Acrobat both display the correct page number and will goto that page (including going to "xi"). Before we fixed this, those display programs did not know how the pages were numbered, and just (incorrectly) counted forward from one. Now the document meets standard page numbering conventions, and the PDF display programs are aware of the true page numbers. > > Bill > > On Apr 7, 2008, at 1:18 PM, Jeff Squyres wrote: > > > Overall > > ======= > > > > - Frontage numbering is still roman numerals -- I thought we agreed to > > have the physical and PDF page numbers agree. > > > > William Gropp > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > 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) From rabenseifner at [hidden] Mon Apr 7 14:43:25 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Mon, 07 Apr 2008 21:43:25 +0200 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: Please do not change any interfaces. All "const" discussion is moved to MPI-2.2. This was a decision of the Forum at March meeting. Best regards Rolf On Mon, 7 Apr 2008 11:32:40 -0700 (PDT) "Bronis R. de Supinski" wrote: > > Jeff: > > You should send the individual issues to the chapter owners. > > I will try to look over the issues for chapters 11 and 14. > I don't have a strong opinon on either of them and will > certainly delete the "const" in chapter 14 if others agree. > > Bronis > > > > > On Mon, 7 Apr 2008, Jeff Squyres wrote: > > > While reading the April 1 MPI-2.1 document for C++ and chapter 13 > > issues, I itemized a list of other issues that I found. Some may want > > to be pushed off to 2.2 (I have noted all of these with "--> This will > > require a vote") -- I leave these up to the Forum to decide -- but > > others should be fixed in 2.1. > > > > Enjoy. > > > > ----- > > > > April 7 2008 > > Comments on MPI-2.1 April 1, 2008 document > > > > (notation: pX.Y = page X, line Y) > > > > Overall > > ======= > > > > - Frontage numbering is still roman numerals -- I thought we agreed to > > have the physical and PDF page numbers agree. > > > > - Some function pointer typedefs are "_function", others are "_fn" > > We should be consistent throughout the text. > > > > Intro chapter > > ============= > > > > - p5.2: Two open source MPI implementations are cited that are no > > longer relevant. This entire sentence should be removed. Indeed, > > the language in the overall paragraph is forward-looking -- it > > should probably be re-worked to be in the present tense. > > > > - p6.46: Chapter 13 discusses Fortran issues (not Fortran 90 issues), > > and also discusses language interoperability issues. > > > > - p7.11: Looks like a broken LaTeX reference. > > > > Terms and Conventions > > ===================== > > > > - p9.40-10.10: The C and Fortran language neutral name do not include > > the prefix "MPI_", but the C++ bindings include the prefix "MPI::". > > Shouldn't the C/Fortran bindings be "MPI_CLASS_ACTION_SUBSET" > > (etc.)? > > > > - p10.35: due to the decision from last meeting (sort out the > > IN/OUT/INOUT mess in MPI-2.2), the language should be softened in > > this paragraph and the full paragraph following this one (because > > they contradict each other). Specifically, I propose changing: > > > > 10.35: Thus, in C++, IN aguments are either references... > > to > > Thus, in C++, IN arguments are usually either references... > > > > - p11.22: "Fortran in this document refers to Fortran 90". For > > MPI-2.1, it is probably suitable to leave this, but we might want to > > make a statement (footnote or parenthetical) that it is expected to > > be updated in future MPI spec revisions. > > > > > > Point-to-Point Communication > > ============================ > > > > - p66.33: Why is the request argument to the C bindings MPI_CANCEL > > take a pointer? The language neutral binding is IN, and the C++ > > binding is const. This seems to be a contradiction. > > --> This cannot be changed easily because every MPI implementation > > uses (MPI_Request *) as the type. > > > > - p83.29: extra space: "( int count," > > > > - p92.43: mising "const" before "void* location". Adding "const" > > will not break any user codes or MPI implementations. > > --> This will require a vote. > > > > - p95.47-48: remove "const" before lb an extent arguments. > > Removing "const" will not break any user codes or MPI > > implementations. > > --> This will require a vote. > > > > Collective Communications > > ========================= > > > > - p123.32: "relaxed" uses quote marks in the wrong direction > > > > - p123.27: should say "MPI-1" instead of "MPI-1.2" > > > > Groups, Contexts, and Communicators > > =================================== > > > > - p186.5: Descriptions for the C++ bindings need to be included here, > > since they are different than the C bindings. The text from 13.1.7 > > would seem to be sufficient. > > > > - p214.32: Missing "const" before "void* attribute_val_in" (datatype > > callback argument is const) > > --> This will require a vote. > > > > - p214.36: Delete function comm argument should be const (?) > > --> This will require a vote. > > > > - p219.5: Missing "const" before "void* attribute_val_in" (datatype > > callback argument is const) > > --> This will require a vote. > > > > - p219.9: Delete function win argument should be const (?) > > --> This will require a vote. > > > > - p221.44: Delete function type argument should be const (?) > > --> This will require a vote. > > > > MPI Environmental Management > > ============================ > > > > - p248.3: Earlier in the document, references are made to v1.3. Is > > that not a valid tuple to return from MPI_GET_VERSION? > > > > - p249.45: Remove duplicate C++ binding > > > > - p254.21: Remove erroneous MPI::Intracomm::Create C++ binding > > > > - p255.2: First argument (comm handle reference) to errhandler > > function should be const. > > --> This will require a vote. > > > > - p256.27: First argument (win handle reference) to errhandler > > function should be const. > > --> This will require a vote. > > > > - p257.41: First argument (file handle reference) to errhandler > > function should be const. > > --> This will require a vote. > > > > - p258.39: Delete duplicate C++ binding > > > > - p259.13: Delete duplicate C++ binding > > > > - p260.36-43: First letter of description should be capitolized to be > > consistent with rest of list. > > > > - p261.42: Delete duplicate C++ binding > > > > - p263.21-23: Delete duplicate C++ bindings > > > > - p264.22: Delete duplicate C++ binding > > > > - p267.24: Delete duplicate C++ binding > > > > - p267.42: Delete duplicate C++ binding > > > > Process Creation and Management > > =============================== > > > > - p288.11: Function should be const. > > --> This will require a vote. > > > > - p288.15: Function should be const. > > --> This will require a vote. > > > > External Interfaces > > =================== > > > > - p344.39: Arguments of query_fn, free_fn, and cancel_fn need to have > > *'s. This is a consistency issue (the rest of the standard uses > > "*" for function pointer parameters), not a correctness issue -- > > works both ways. Should not break any user code or MPI > > implementations. > > > > I/O > > === > > > > - p419.43: datatype argument should be const > > > > Language Bindings > > ================= > > > > - p437.18: Delete first sentence of paragraph > > > > - p437.22: Delete "original" > > > > - p437.24-29: Delete first and last sentences of paragraph > > > > - p437.29: New last sentence, "See Annex A.4.19 for a function cross > > reference." > > > > - p438.11: Delete "for MPI-1" > > > > - p438.14-37: Join the two namespaces together and delete the > > "Additionally, the following classes defined for MPI-2:" text. > > Re-sort the class names as appropriate. > > > > - p439.2: Delete last sentence ("To maintain ... in [23].") > > > > - p442: Table 13.1 is redundant with Annex A.1. However, the > > following C++ types are missing from Annex A.1: > > > > MPI::SIGNED_CHAR > > MPI::BOOL > > MPI::COMPLEX > > MPI::DOUBLE_COMPLEX > > MPI::LONG_DOUBLE_COMPLES > > > > - p442: Table 13.2 is redundant with Annex A.1 > > > > - p445.5-11: These functions are not listed in Annex A > > > > - p445.36-38: Remove this entire paragraph ("Compilers that do not > > support..."). This feature has been a part of C++ since C++98, and > > exists in all modern C++ compilers. > > > > - p446.7-17: Declarations for the MPI::Exceptions class are missing > > from Annex A > > > > - p448.47: Remove trailing "/" from "OUT/" > > > > - p450.26-44: The bullet list is wholly redundant with section 2.6.2. > > > > - p456.27-29: VOLATILE is in Fortran 200x; reword first sentence from: > > "In the longer term, the attribute VOLATILE is under > > consideration for Fortran 2000 and would give the buffer or > > variable the properties needed, but it would inhibit > > optimization of any code containing the buffer or variable." > > to > > "The VOLATILE attribute, available in later versions of Fortran, > > would give the buffer or variable the properties needed, but it > > would inhibit optimization of any code containing the buffer or > > variable." > > > > - p459.11-15: Delete paragraph > > > > - p462.43-45: Delete paragraph > > > > - p463.17-18: Delete first sentence; delete "In MPI-2," > > > > - p467.23: There is an extra space before "MPI_FINALIZE" > > > > - p468.16-39: None of these functions appear in Annex A (they > > should!) > > > > - p469.41 and 44: These functions do not appear in Annex A (they > > should!) > > > > - p470.46: Change sentence from: > > "It is important to note that all C++ objects and their > > corresponding C handles..." > > to > > "It is important to note that all C++ objects with > > corresponding C handles..." > > I.e., this sentence is referring only to C++ handles that actually > > have corresponding C handles (e.g., not > > MPI::ERRORS_THROW_EXCEPTIONS). > > > > Profiling Interface > > =================== > > > > - p481.4: Delete "const" > > --> This may require a vote. > > > > Annex A > > ======= > > > > - p494.15: s/Fortran/Fortran only > > > > - p494.30: Missing MPI::ERRORS_THROW_EXCEPTIONS > > > > - p495.18-19 and 33-34: MPI_BYTE and MPI_PACKED are listed in two > > separate tables. > > > > - p495.30: MPI::COMPLEX should be MPI::F_COMPLEX > > > > - p495.38: Looks like a blank extra 3rd column is in this table > > > > - p495.bottom: Missing table for "C++ only" datatypes: > > MPI::BOOL > > MPI::COMPLEX > > MPI::DOUBLE_COMPLEX > > MPI::LONG_DOUBLE_COMPLEX > > MPI::SIGNED_CHAR > > > > - p496.1: Add ", no Fortran" before the ")" > > > > - p496.10, s/Fortran/Fortran only/ > > > > - p496.27-30: Alignment of table entries should be to the left, not > > centered. > > > > - p544.13: Many of the prototypes for Clone() and Dup() are missing > > > > - p547.all: Many doubles of C++ bindings; likely because of errors in > > the chapter text. > > > > - p554.41: Do we need an empty deprecated functions section? > > > > - p555.45-46: Forgot to mention MPI_ERRCODES_IGNORE, > > MPI_F_STATUSES_IGNORE, and MPI_F_STATUS_IGNORE > > > > - p556.bottom: Missing prototypes for the MPI::Exceptions class > > > > -- > > Jeff Squyres > > Cisco Systems > > > > _______________________________________________ > > 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 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) From rabenseifner at [hidden] Tue Apr 8 07:33:58 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 08 Apr 2008 14:33:58 +0200 Subject: [Mpi-21] MPI-2.1 April 1 document comments In-Reply-To: Message-ID: Hi Jeff, as with all reviews, I've put it into http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt User / Password as usual: mpi21 / mpi21 Most of your proposals in Binding, I commented with R2 to give it back to you for implementing it. Best regards Rolf On Mon, 7 Apr 2008 11:18:32 -0700 Jeff Squyres wrote: > While reading the April 1 MPI-2.1 document for C++ and chapter 13 > issues, I itemized a list of other issues that I found. Some may want > to be pushed off to 2.2 (I have noted all of these with "--> This will > require a vote") -- I leave these up to the Forum to decide -- but > others should be fixed in 2.1. > > Enjoy. > > ----- > > April 7 2008 > Comments on MPI-2.1 April 1, 2008 document > > (notation: pX.Y = page X, line Y) > > Overall > ======= > > - Frontage numbering is still roman numerals -- I thought we agreed to > have the physical and PDF page numbers agree. > > - Some function pointer typedefs are "_function", others are "_fn" > We should be consistent throughout the text. > > Intro chapter > ============= > > - p5.2: Two open source MPI implementations are cited that are no > longer relevant. This entire sentence should be removed. Indeed, > the language in the overall paragraph is forward-looking -- it > should probably be re-worked to be in the present tense. > > - p6.46: Chapter 13 discusses Fortran issues (not Fortran 90 issues), > and also discusses language interoperability issues. > > - p7.11: Looks like a broken LaTeX reference. > > Terms and Conventions > ===================== > > - p9.40-10.10: The C and Fortran language neutral name do not include > the prefix "MPI_", but the C++ bindings include the prefix "MPI::". > Shouldn't the C/Fortran bindings be "MPI_CLASS_ACTION_SUBSET" > (etc.)? > > - p10.35: due to the decision from last meeting (sort out the > IN/OUT/INOUT mess in MPI-2.2), the language should be softened in > this paragraph and the full paragraph following this one (because > they contradict each other). Specifically, I propose changing: > > 10.35: Thus, in C++, IN aguments are either references... > to > Thus, in C++, IN arguments are usually either references... > > - p11.22: "Fortran in this document refers to Fortran 90". For > MPI-2.1, it is probably suitable to leave this, but we might want to > make a statement (footnote or parenthetical) that it is expected to > be updated in future MPI spec revisions. > > > Point-to-Point Communication > ============================ > > - p66.33: Why is the request argument to the C bindings MPI_CANCEL > take a pointer? The language neutral binding is IN, and the C++ > binding is const. This seems to be a contradiction. > --> This cannot be changed easily because every MPI implementation > uses (MPI_Request *) as the type. > > - p83.29: extra space: "( int count," > > - p92.43: mising "const" before "void* location". Adding "const" > will not break any user codes or MPI implementations. > --> This will require a vote. > > - p95.47-48: remove "const" before lb an extent arguments. > Removing "const" will not break any user codes or MPI > implementations. > --> This will require a vote. > > Collective Communications > ========================= > > - p123.32: "relaxed" uses quote marks in the wrong direction > > - p123.27: should say "MPI-1" instead of "MPI-1.2" > > Groups, Contexts, and Communicators > =================================== > > - p186.5: Descriptions for the C++ bindings need to be included here, > since they are different than the C bindings. The text from 13.1.7 > would seem to be sufficient. > > - p214.32: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p214.36: Delete function comm argument should be const (?) > --> This will require a vote. > > - p219.5: Missing "const" before "void* attribute_val_in" (datatype > callback argument is const) > --> This will require a vote. > > - p219.9: Delete function win argument should be const (?) > --> This will require a vote. > > - p221.44: Delete function type argument should be const (?) > --> This will require a vote. > > MPI Environmental Management > ============================ > > - p248.3: Earlier in the document, references are made to v1.3. Is > that not a valid tuple to return from MPI_GET_VERSION? > > - p249.45: Remove duplicate C++ binding > > - p254.21: Remove erroneous MPI::Intracomm::Create C++ binding > > - p255.2: First argument (comm handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p256.27: First argument (win handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p257.41: First argument (file handle reference) to errhandler > function should be const. > --> This will require a vote. > > - p258.39: Delete duplicate C++ binding > > - p259.13: Delete duplicate C++ binding > > - p260.36-43: First letter of description should be capitolized to be > consistent with rest of list. > > - p261.42: Delete duplicate C++ binding > > - p263.21-23: Delete duplicate C++ bindings > > - p264.22: Delete duplicate C++ binding > > - p267.24: Delete duplicate C++ binding > > - p267.42: Delete duplicate C++ binding > > Process Creation and Management > =============================== > > - p288.11: Function should be const. > --> This will require a vote. > > - p288.15: Function should be const. > --> This will require a vote. > > External Interfaces > =================== > > - p344.39: Arguments of query_fn, free_fn, and cancel_fn need to have > *'s. This is a consistency issue (the rest of the standard uses > "*" for function pointer parameters), not a correctness issue -- > works both ways. Should not break any user code or MPI > implementations. > > I/O > === > > - p419.43: datatype argument should be const > > Language Bindings > ================= > > - p437.18: Delete first sentence of paragraph > > - p437.22: Delete "original" > > - p437.24-29: Delete first and last sentences of paragraph > > - p437.29: New last sentence, "See Annex A.4.19 for a function cross > reference." > > - p438.11: Delete "for MPI-1" > > - p438.14-37: Join the two namespaces together and delete the > "Additionally, the following classes defined for MPI-2:" text. > Re-sort the class names as appropriate. > > - p439.2: Delete last sentence ("To maintain ... in [23].") > > - p442: Table 13.1 is redundant with Annex A.1. However, the > following C++ types are missing from Annex A.1: > > MPI::SIGNED_CHAR > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLES > > - p442: Table 13.2 is redundant with Annex A.1 > > - p445.5-11: These functions are not listed in Annex A > > - p445.36-38: Remove this entire paragraph ("Compilers that do not > support..."). This feature has been a part of C++ since C++98, and > exists in all modern C++ compilers. > > - p446.7-17: Declarations for the MPI::Exceptions class are missing > from Annex A > > - p448.47: Remove trailing "/" from "OUT/" > > - p450.26-44: The bullet list is wholly redundant with section 2.6.2. > > - p456.27-29: VOLATILE is in Fortran 200x; reword first sentence from: > "In the longer term, the attribute VOLATILE is under > consideration for Fortran 2000 and would give the buffer or > variable the properties needed, but it would inhibit > optimization of any code containing the buffer or variable." > to > "The VOLATILE attribute, available in later versions of Fortran, > would give the buffer or variable the properties needed, but it > would inhibit optimization of any code containing the buffer or > variable." > > - p459.11-15: Delete paragraph > > - p462.43-45: Delete paragraph > > - p463.17-18: Delete first sentence; delete "In MPI-2," > > - p467.23: There is an extra space before "MPI_FINALIZE" > > - p468.16-39: None of these functions appear in Annex A (they > should!) > > - p469.41 and 44: These functions do not appear in Annex A (they > should!) > > - p470.46: Change sentence from: > "It is important to note that all C++ objects and their > corresponding C handles..." > to > "It is important to note that all C++ objects with > corresponding C handles..." > I.e., this sentence is referring only to C++ handles that actually > have corresponding C handles (e.g., not > MPI::ERRORS_THROW_EXCEPTIONS). > > Profiling Interface > =================== > > - p481.4: Delete "const" > --> This may require a vote. > > Annex A > ======= > > - p494.15: s/Fortran/Fortran only > > - p494.30: Missing MPI::ERRORS_THROW_EXCEPTIONS > > - p495.18-19 and 33-34: MPI_BYTE and MPI_PACKED are listed in two > separate tables. > > - p495.30: MPI::COMPLEX should be MPI::F_COMPLEX > > - p495.38: Looks like a blank extra 3rd column is in this table > > - p495.bottom: Missing table for "C++ only" datatypes: > MPI::BOOL > MPI::COMPLEX > MPI::DOUBLE_COMPLEX > MPI::LONG_DOUBLE_COMPLEX > MPI::SIGNED_CHAR > > - p496.1: Add ", no Fortran" before the ")" > > - p496.10, s/Fortran/Fortran only/ > > - p496.27-30: Alignment of table entries should be to the left, not > centered. > > - p544.13: Many of the prototypes for Clone() and Dup() are missing > > - p547.all: Many doubles of C++ bindings; likely because of errors in > the chapter text. > > - p554.41: Do we need an empty deprecated functions section? > > - p555.45-46: Forgot to mention MPI_ERRCODES_IGNORE, > MPI_F_STATUSES_IGNORE, and MPI_F_STATUS_IGNORE > > - p556.bottom: Missing prototypes for the MPI::Exceptions class > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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) From rabenseifner at [hidden] Tue Apr 8 08:32:59 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 08 Apr 2008 15:32:59 +0200 Subject: [Mpi-21] Newest updates In-Reply-To: Message-ID: Updated chapters: 6. Process Topologies (by Jesper Traeff) 8. Miscellany (by Jesper Traeff) 10. One-sided (by Jesper Traeff) A. Annex Language Bindings (Jeff's comments implemented) Annex A.4 is now sorted again by the routines names. See http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf (should be used only for controling) (Review references should be done normally to Draft Apr. 1, 2008) and http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt 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) From rabenseifner at [hidden] Tue Apr 8 13:03:11 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 08 Apr 2008 20:03:11 +0200 Subject: [Mpi-21] Newest updates In-Reply-To: Message-ID: Please have a look at the last pages of http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf At the end, all Index data is now separated into 4 Indexes. - The entries in the C++ index should be corrected that they go directly into the const index. - The Callback index is not complete. 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) From rabenseifner at [hidden] Tue Apr 8 15:27:09 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 08 Apr 2008 22:27:09 +0200 Subject: [Mpi-21] pt2pt chapter - split into 2 chapters? Message-ID: >>> please do not forget to svn commit your current chapter pt2pt.tex and credits.tex source this evening and give me back the write-token. <<< Rich, I'm not sure wether you are doing this already: Chapter 3 to 14 have each 38 pages in average, but Chapter 3 has 100 pages. The last 50 pages are 3.12-3.14, the derived datatypes together with pack and unpack. These 50 pages are independent from normal pt2pt communication, because needed also in all other communication. I would recommend to spilt it into 2 chapters. (It was already proposed from someone else.) If nobody is against, and you have not done already, I would do it tomorrow together with the corrections based on the last reviews. Please do not forget to svn commit and to send me an email, giving me back the allowance to write (write-token). (If you have done nothing, then I need only the email.) ASAP I'll transfer the token back to you. Have you already looked at the new Indexes? My next mail looks at Chapter 11. 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) From rabenseifner at [hidden] Tue Apr 8 15:46:37 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Tue, 08 Apr 2008 22:46:37 +0200 Subject: [Mpi-21] Rest of MPI-2.1 External interfaces into other chapters. Message-ID: Bronis, George, Dick (and Rich), Have already implemented the merge? Decoding a Datatype is already moved to Datatypes. Naming Objects, I would move it after 5.7 Caching. And the rest, I expect you have done a nice merge. As you know, I would like to get the write-token this evening. Please svn commit you current status this evening and send me an email with the files for wich I get the right to write from you. Any comments on the new Indexes? Best regards Rolf On Thu, 3 Apr 2008 15:19:55 -0400 George Bosilca wrote: > Bronis, > > If the data-type section get moved into the chapter 3 it make sense to merge the leftover of the chapter 11 with chapter 7, as long as we choose a right name. "MPI Environmental Management" is not the right chapter for "Generalized Requests". But of course these are just details. > > I'll get in touch with you asap to see how we can coordinate. > > Thanks, > george. 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) From bronis at [hidden] Tue Apr 8 16:20:51 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Tue, 8 Apr 2008 14:20:51 -0700 (PDT) Subject: [Mpi-21] Rest of MPI-2.1 External interfaces into other chapters. In-Reply-To: Message-ID: Rolf: Re: > Have already implemented the merge? No. > Decoding a Datatype is already moved to Datatypes. Yes. > Naming Objects, I would move it after 5.7 Caching. Works for me. > And the rest, I expect you have done a nice merge. Not yet. Too busy with the SC deadline, the EuroPVM/MPI deadline and an internal proposal deadline. Frankly, I don't expect to get back to this until next week. > As you know, I would like to get the write-token this evening. > Please svn commit you current status this evening and send > me an email with the files for wich I get the right to write > from you. You've got the token as far as I am concerned. > Any comments on the new Indexes? They look nice. Bronis > > Best regards > Rolf > > > On Thu, 3 Apr 2008 15:19:55 -0400 > George Bosilca wrote: > > Bronis, > > > > If the data-type section get moved into the chapter 3 it make sense to merge the leftover of the chapter 11 with chapter 7, as long as we choose a right name. "MPI Environmental Management" is not the right chapter for "Generalized Requests". But of course these are just details. > > > > I'll get in touch with you asap to see how we can coordinate. > > > > Thanks, > > george. > > > > 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) > From jsquyres at [hidden] Tue Apr 8 16:54:36 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Tue, 8 Apr 2008 14:54:36 -0700 Subject: [Mpi-21] Newest updates In-Reply-To: Message-ID: The new indexes are a good idea, but they seem a bit inconsistent: - The examples index is a mix of upper and lower case MPI function names - The MPI constant index has only 1 C++ constant listed - I see weird entries in the MPI constant index, such as: MPI_ERR_... (I'm not abbreviating -- there's actually an "MPI_ERR_..." entry) MPI_Delete_function MPI_Copy_function MPI_Aint ...and others - I'm not sure what the MPI C++ index is; the only item listed that does not have an equivalent in C is MPI::ERRORS_THROW_EXCEPTIONS - The MPI function index has weird entries, similar to the constant index, such as: MPI_ MPI_*_FREE MPI_{TYPE,COMM,WIN}_CREATE_KEYVAL MPI_Comm_delete_attr_function ...and others - The MPI function index also has a mix of upper and lower case MPI function names On Apr 8, 2008, at 11:03 AM, Rolf Rabenseifner wrote: > Please have a look at the last pages of > http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf > > At the end, all Index data is now separated into 4 Indexes. > - The entries in the C++ index should be corrected that > they go directly into the const index. > - The Callback index is not complete. > > 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.mpi-forum.org/mailman/listinfo.cgi/mpi-21 -- Jeff Squyres Cisco Systems From treumann at [hidden] Tue Apr 8 18:46:27 2008 From: treumann at [hidden] (Richard Treumann) Date: Tue, 8 Apr 2008 19:46:27 -0400 Subject: [Mpi-21] Chapter 5 In-Reply-To: Message-ID: Rolf - My attempt to check in the file did not work and since I am not familiar with svn I did not try very long to debug the failure. The file is attached to this email. If you can get it into the repository you have the write token. (See attached file: context.tex) Chapter 5 - items needing Forum feedback (references are to April 1 draft) 1) 171:28-29 We point to a couple 15 year old papers to give background on using MPI to write libraries. It seems to me the concepts no longer require this backup. They have been around for long enough to be current practice. Is there a reason to keep the pointers? 2) 192:8-13 Bogus advise about just playing with the reference count to implement MPI_COMM_DUP (I think Rolf has already captured this for MPI 2.2) 3) 202:31-35 The wierd suggestion that intercommunicator groups may not be required to be disjoint should come out. Everything else is pretty clear that they ARE disjoint. As far as I can see this statement falls into the catagory of "We could have made a different choice when we wrote MPI-1". The decision was made that the groups are disjoint so this editorial aside should be removed. 4) The discussion of attribute caching needs significant rework. It has paragraphs from when only communicators supported caching and paragraphs about adding caching support to windows and datatypes. It should be reworded to describe caching as it applies to all three object types and explain who there is no WIN_DUP while there is a TYPE_DUP and a COMM_DUP. (and therefore no attribute copy functions for windows.) 5) Jeff Squires has pointed out a need for explanation of the C++ clone functions on 186:1-5 and to me it looks like a sentence or two from a C++ guru along with a pointer to section 13.1.7 would do. Perhaps add: Please see section ____ page ___ for further discussion about the C++ bindings for Dup() and Clone(). where ____ page ___ is a link to 13.1.7. (I did not want to try to add a LaTex link so I did not do any of this change) The changes I have made are pretty straightforward. Dick 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 * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: context.tex Type: application/octet-stream Size: 155381 bytes Desc: context.tex URL: From jsquyres at [hidden] Wed Apr 9 01:12:19 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Tue, 8 Apr 2008 23:12:19 -0700 Subject: [Mpi-21] Language bindings Message-ID: I have committed the changes to the language bindings chapter (r75). ------------- I had two questions about Rolf's list for chapter 13: JMS WHY IS THIS AN MPI-2.2 ISSUE? 32.r 22 p463.17-18: Delete first sentence; delete "In MPI-2," JMS WHY IS THIS A QUESTION MARK? 32.v ? p470.46: Change sentence from: "It is important to note that all C++ objects and their corresponding C handles..." to "It is important to note that all C++ objects with corresponding C handles..." I.e., this sentence is referring only to C++ handles that actually have corresponding C handles (e.g., not MPI::ERRORS_THROW_EXCEPTIONS). ------------- One answer to a question in Rolf's list: JMS THE NAMES THAT ARE THERE ARE GOOD 32.j' ? Which names should be visible in the Index for Dup and Clone? ------------- And here's the items that I completed: JMS DONE 32.a R2 p437.18: Delete first sentence of paragraph Editor's comment: Please check the "this interface" in the next sentence. This is a backward reference to the first sentence. JMS DONE 32.b R2 p437.22: Delete "original" Editor's comment: Please check "original ... was based". Removing "original" may need further corrections. JMS DONE 32.c R2 p437.24-29: Delete first and last sentences of paragraph Editor's comment: See also Review item 28.q JMS DONE 32.d R2 p437.29: New last sentence, "See Annex A.4.19 for a function cross reference." JMS DONE 32.e R2 p438.11: Delete "for MPI-1" JMS DONE 32.f R2 p438.14-37: Join the two namespaces together and delete the "Additionally, the following classes defined for MPI-2:" text. Re-sort the class names as appropriate. JMS DONE 32.g R2 p439.2: Delete last sentence ("To maintain ... in [23].") JMS DONE 32.k R2 p445.36-38: Remove this entire paragraph ("Compilers that do not support..."). This feature has been a part of C++ since C+ +98, and exists in all modern C++ compilers. JMS DONE 32.p *NO* p459.11-15: Delete paragraph Editor's comment: The first MPI-1 should be substituted by MPI, the second MPI-1 should be removed. The paragraph is still valid. JMS CHANGED MPI-1 to MPI 32.q *NO* p462.43-45: Delete paragraph Editor's comment: The paragraph is still valid. -- Jeff Squyres Cisco Systems From traff at [hidden] Wed Apr 9 01:50:22 2008 From: traff at [hidden] (Jesper Larsson Traeff) Date: Wed, 9 Apr 2008 08:50:22 +0200 Subject: [Mpi-21] Chapter 5 In-Reply-To: Message-ID: <20080409065022.GA434@fourier.it.neclab.eu> Dick, Rolf, all, On Tue, Apr 08, 2008 at 07:46:27PM -0400, Richard Treumann wrote: > > 4) The discussion of attribute caching needs significant rework. It has > paragraphs from when only communicators supported caching and paragraphs > about adding caching support to windows and datatypes. It should be > reworded to describe caching as it applies to all three object types and > explain who there is no WIN_DUP while there is a TYPE_DUP and a COMM_DUP. > (and therefore no attribute copy functions for windows.) > I agree with that. A not so modest proposal (requiring work) would be to have a seperate chapter on object caching, and merge that with the chapter on the info object (which is too short on its own, and still has the hopeless "miscellany" title)? Jesper * -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2180 bytes Desc: smime.p7s URL: From gropp at [hidden] Wed Apr 9 08:37:47 2008 From: gropp at [hidden] (William Gropp) Date: Wed, 9 Apr 2008 08:37:47 -0500 Subject: [Mpi-21] Rest of MPI-2.1 External interfaces into other chapters. In-Reply-To: Message-ID: I can't build the language bindings appendix because the new scripts assume new GNU versions of some standard Unix commands (like sort), and my Mac doesn't have those versions. Can we stick with the more portable versions (e.g., in MAKE-APPLANG, don't use --key, which my sort command does not recognize and is, I believe, a GNU extension)? While we're at it, pdfinfo isn't standard either - is this really necessary for the Make (which for me always fails at this step)? There's a pdfinfo command for Macs, but it pops up a GUI and that's probably not intended (and certainly not appropriate). Bill William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign * -------------- next part -------------- An HTML attachment was scrubbed... URL: From treumann at [hidden] Wed Apr 9 08:39:59 2008 From: treumann at [hidden] (Richard Treumann) Date: Wed, 9 Apr 2008 09:39:59 -0400 Subject: [Mpi-21] Chapter 5 In-Reply-To: <20080409065022.GA434@fourier.it.neclab.eu> Message-ID: Someone also suggested that object naming move to join caching. If we take Jesper's suggestion then object naming would become part of this new chapter too. It all makes sense to me but I do not know who has the cycles to do the work. I do not Dick 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 mpi-21-bounces_at_[hidden] wrote on 04/09/2008 02:50:22 AM: > > Dick, Rolf, all, > > On Tue, Apr 08, 2008 at 07:46:27PM -0400, Richard Treumann wrote: > > > > 4) The discussion of attribute caching needs significant rework. It has > > paragraphs from when only communicators supported caching and paragraphs > > about adding caching support to windows and datatypes. It should be > > reworded to describe caching as it applies to all three object types and > > explain who there is no WIN_DUP while there is a TYPE_DUP and a COMM_DUP. > > (and therefore no attribute copy functions for windows.) > > > I agree with that. A not so modest proposal (requiring work) would be > to have a seperate chapter on object caching, and merge that with the > chapter on the info object (which is too short on its own, and still has > the hopeless "miscellany" title)? > > Jesper > > [attachment "smime.p7s" deleted by Richard > Treumann/Poughkeepsie/IBM] _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 * -------------- next part -------------- An HTML attachment was scrubbed... URL: From gropp at [hidden] Wed Apr 9 08:40:51 2008 From: gropp at [hidden] (William Gropp) Date: Wed, 9 Apr 2008 08:40:51 -0500 Subject: [Mpi-21] Chapter 5 In-Reply-To: Message-ID: <4502BA8A-4AE6-4917-A828-8F57E5D6922A@mcs.anl.gov> Here are my comments on these points. On Apr 8, 2008, at 6:46 PM, Richard Treumann wrote: > Rolf - > > My attempt to check in the file did not work and since I am not > familiar with svn I did not try very long to debug the failure. The > file is attached to this email. If you can get it into the > repository you have the write token. > > (See attached file: context.tex) > > Chapter 5 - items needing Forum feedback (references are to April 1 > draft) > > 1) 171:28-29 We point to a couple 15 year old papers to give > background on using MPI to write libraries. It seems to me the > concepts no longer require this backup. They have been around for > long enough to be current practice. Is there a reason to keep the > pointers? > I think we should edit and add to this, not drop it. I still hear people say that "MPI was derived from PVM," which is not true and which this historical context makes clear. > > > 2) 192:8-13 Bogus advise about just playing with the reference > count to implement MPI_COMM_DUP (I think Rolf has already captured > this for MPI 2.2) > Agreed. > > > 3) 202:31-35 The wierd suggestion that intercommunicator groups may > not be required to be disjoint should come out. Everything else is > pretty clear that they ARE disjoint. As far as I can see this > statement falls into the catagory of "We could have made a > different choice when we wrote MPI-1". The decision was made that > the groups are disjoint so this editorial aside should be removed. > This needs to be removed because it is one of the adopted errata. No discussion should be needed. > > > 4) The discussion of attribute caching needs significant rework. It > has paragraphs from when only communicators supported caching and > paragraphs about adding caching support to windows and datatypes. > It should be reworded to describe caching as it applies to all > three object types and explain who there is no WIN_DUP while there > is a TYPE_DUP and a COMM_DUP. (and therefore no attribute copy > functions for windows.) > Agreed. > > > 5) Jeff Squires has pointed out a need for explanation of the C++ > clone functions on 186:1-5 and to me it looks like a sentence or > two from a C++ guru along with a pointer to section 13.1.7 would > do. Perhaps add: > Please see section ____ page ___ for further discussion about > the C++ bindings for Dup() and Clone(). where ____ page ___ is a > link to 13.1.7. (I did not want to try to add a LaTex link so I > did not do any of this change) > > Agreed. > > The changes I have made are pretty straightforward. > > Dick > > 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 > _______________________________________________ > > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign * -------------- next part -------------- An HTML attachment was scrubbed... URL: From rabenseifner at [hidden] Thu Apr 10 12:12:12 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 10 Apr 2008 19:12:12 +0200 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you Message-ID: >> write-token again to the chapter authors << >> - but only until Saturday 8:00 European GMT << Hi all authors and reviewers, Please read this mail carfully, if you want to make any further modification of the text. You must now call svn update to get the newest release!! We have a again a consistent version. Nearly all of http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt is now implemented in the tex-source. Only a few items are still open, see statistics at the beginning. You can view the current version (it is svn revision 92) at http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf It is only today and Friday remaining for finishing MPI-2.1. I give back the write-token to the authors. On Saturday morning European time, I take the write-token automatically on Saturday morning to build final pdf for the reviews. As I can see, many chapter authors made fine cleaning to the text. All larger changes should be defered to MPI-2.2! Especially the merge of MPI Environment (inquiry.tex), Misc (misc-2.tex) and External Interfaces (ei-2.tex) to one chapter "MPI Environment and Miscellany" (with 45 pages) may be defered also to MPI-2.2. Up to now, I was able to check most changes and they look fine. 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) From rabenseifner at [hidden] Thu Apr 10 12:29:10 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 10 Apr 2008 19:29:10 +0200 Subject: [Mpi-21] old-style sort in MAKE-APPLANG In-Reply-To: Message-ID: To all who had problems with the sort --key in MAKE-APPLANG I commited a new MAKE-APPLANG (rev 93) that should work on any Linux or MAC system. 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) From gropp at [hidden] Thu Apr 10 12:37:48 2008 From: gropp at [hidden] (William Gropp) Date: Thu, 10 Apr 2008 12:37:48 -0500 Subject: [Mpi-21] old-style sort in MAKE-APPLANG In-Reply-To: Message-ID: Thanks! Bill On Apr 10, 2008, at 12:29 PM, Rolf Rabenseifner wrote: > To all who had problems with the sort --key in MAKE-APPLANG > > I commited a new MAKE-APPLANG (rev 93) > that should work on any Linux or MAC system. > > 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.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign * -------------- next part -------------- An HTML attachment was scrubbed... URL: From gropp at [hidden] Thu Apr 10 12:47:27 2008 From: gropp at [hidden] (William Gropp) Date: Thu, 10 Apr 2008 12:47:27 -0500 Subject: [Mpi-21] illegal and invalid Message-ID: In reading through Rolf's excellent list of issues, I noted a comment about "illegal" datatypes. We really should use "valid" and "invalid" rather then "legal" and "illegal", since MPI is, at least not yet, the law :) Something for the 2.2 edits.... (The GNU Coding standards make a point of rejecting the use of illegal, BTW.) Bill William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign * -------------- next part -------------- An HTML attachment was scrubbed... URL: From moody20 at [hidden] Fri Apr 11 17:22:10 2008 From: moody20 at [hidden] (Adam Moody) Date: Fri, 11 Apr 2008 15:22:10 -0700 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you In-Reply-To: Message-ID: <47FFE492.8020509@llnl.gov> Hi Rolf, I have checked in my changes for the Collectives chapter. It's ready to be reviewed by the collective chapter reviewers. -Adam Rolf Rabenseifner wrote: >>>write-token again to the chapter authors << >>>- but only until Saturday 8:00 European GMT << >>> >>> > >Hi all authors and reviewers, > >Please read this mail carfully, if you want to make any further >modification of the text. > >You must now call > svn update >to get the newest release!! >We have a again a consistent version. Nearly all of > > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > >is now implemented in the tex-source. >Only a few items are still open, see statistics at the beginning. > >You can view the current version (it is svn revision 92) at > > http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf > >It is only today and Friday remaining for finishing MPI-2.1. >I give back the write-token to the authors. > >On Saturday morning European time, I take the write-token >automatically on Saturday morning to build final pdf for the >reviews. > >As I can see, many chapter authors made fine cleaning to the text. >All larger changes should be defered to MPI-2.2! >Especially the merge of MPI Environment (inquiry.tex), Misc (misc-2.tex) >and External Interfaces (ei-2.tex) >to one chapter "MPI Environment and Miscellany" (with 45 pages) >may be defered also to MPI-2.2. > >Up to now, I was able to check most changes and they look fine. > >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.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > > From rabenseifner at [hidden] Sat Apr 12 10:14:46 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sat, 12 Apr 2008 17:14:46 +0200 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you In-Reply-To: <47FFE492.8020509@llnl.gov> Message-ID: Hi Adam, this is really a good merge that you have done. Good ideas and very carefully implemented. The reviewers can see (nearly) all of your modifications in red. I expect that your reviewersand the Forum will enjoy your modifications. I have restored two minor mods you have done: (Line numbers refer to the new file you'll get with svn update) coll.tex, line 412 - I restored the "intracommunicator" because the categories describe the behavior only on intracommunicators, not on all, e.g., ALLGATHER has one result on intra and two on inter and the wording is "the result". coll.tex, line 491 - restored the word "also". These routines are valid for intra and inter. Writing "apply to inter" may be interpreted that they are only valid for inter. Writing "also apply to inter" should solve this problem. I also colored this sentence red. I hop, this isokay with you. Best regards Rolf On Fri, 11 Apr 2008 15:22:10 -0700 Adam Moody wrote: > Hi Rolf, > I have checked in my changes for the Collectives chapter. It's ready to > be reviewed by the collective chapter reviewers. > -Adam > > Rolf Rabenseifner wrote: > > >>>write-token again to the chapter authors << > >>>- but only until Saturday 8:00 European GMT << > >>> > >>> > > > >Hi all authors and reviewers, > > > >Please read this mail carfully, if you want to make any further > >modification of the text. > > > >You must now call > > svn update > >to get the newest release!! > >We have a again a consistent version. Nearly all of > > > > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > > > >is now implemented in the tex-source. > >Only a few items are still open, see statistics at the beginning. > > > >You can view the current version (it is svn revision 92) at > > > > http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf > > > >It is only today and Friday remaining for finishing MPI-2.1. > >I give back the write-token to the authors. > > > >On Saturday morning European time, I take the write-token > >automatically on Saturday morning to build final pdf for the > >reviews. > > > >As I can see, many chapter authors made fine cleaning to the text. > >All larger changes should be defered to MPI-2.2! > >Especially the merge of MPI Environment (inquiry.tex), Misc (misc-2.tex) > >and External Interfaces (ei-2.tex) > >to one chapter "MPI Environment and Miscellany" (with 45 pages) > >may be defered also to MPI-2.2. > > > >Up to now, I was able to check most changes and they look fine. > > > >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.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 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) From rabenseifner at [hidden] Sat Apr 12 17:05:37 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sun, 13 Apr 2008 00:05:37 +0200 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 Message-ID: Dear chapter author, dear reviewer, This e-mail is the first preparation of the official reading. Please read carefully. Again,we have a stable and consistent draft. It is SVN revision 108 and pdf and ps are on http://www.hlrs.de/mpi/mpi21/doc/ (username and password are mpi21) Nearly all chapters have received an update by the chapters' authors. Not finished is - as far as I can see - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) - Datatypes [it was split from Point-to-point] (Rich Graham) and full MPI-2 based chapters (maybe without need for updates) - Terms (Tony Skjellum) - External Interfaces (Bronis de Supinski) - Profiling (Bronis de Supinski) Therefore, review can start in all chapters, except the datatype chapter. IMPORTANT for authors: If you make further modifications, please be sure that you use the macros and that your modification (or at least an delete-anchor) is printed **red**. (Details on using the macros, see below.) Please check red color in the resulting mpi-report.pdf before you svn commit your changes. As far as I can see, all changes up to now may have no problem for acceptance by the Forum. At this late stage, I would recommend to do only changes that do not need intensive debates at the Forum meeting. Such things would be MPI-2.2 modifications. IMPORTANT for reviewers: - 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). - Please make all comments in the format ---------------------------------------------------------------------------------- 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.) ---------------------------------------------------------------------------------- - Please send only review items that are in the category -- ERROR, must be fixed. - If you want to send an item in the categories -- Nice to have, -- Editorial proposal (like move xxx to yyy), -- Clarification which needs Forum decisions, -- ... then please substitute the __ by 22, because then it should be handled in MPI-2.2. This format is used in http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt where all reviews are filed in. (I'll substitute your xx by the next number. If you have more than 26 items, then please continue with xx.a -- xx.z, yy.a - ...) Please use this format. I'll have only a few minutes between two flights to put all reviews together. WORKPLAN: - The authors get back the write-token until Thursday, Apr. 17. (If you need also Friday Apr. 18, then please inform me!!) - All stuff that is not done until that point, will be defered to MPI-2.2! - I'm on travel and may not be able to respond on e-mails this week. - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the final version for all final reviews and for the official reading. - Version Apr. 17 together with all your review mails will be the basis for the official reading. - Reviews until Friday, Apr. 25. according the format above. - Saturday, Apr. 26: I will put all reviews together to have unique numbers. Best regards Rolf Annex: The rules for authors: The goals of your work as chapter author: ----------------------------------------- - Remove references to MPI-1 and MPI-2. - Substitute by MPI. - Necessary modifications to achieve this goal. With this, we should have a single MPI-2.1 standard that does not "know" the MPI-1 or MPI-2 history of individual functions. ** This should be mainly a task in the area of chapter-introductions. ** Please, never change the wording of function definitions. Exceptions: - There are routines that are deprecated and that are already referenced in a consistent way. My recommendation: Current wording: There are *new* function, and existing are now deprecated. Proposal: There are functions, and there exist also deprecated functions with (nearly) same functionality but deprecated due to some lack in the bindings (or functionality) - There is history information in the frontmatter. - there is a change-log annex with limited memory (only previous version) Technical editing rule: ----------------------- You must identify all of your changes: a) new/modified wording - you are highlighting your new/modified wording with: \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification .... your modified / new wording .... \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification b) Moved paragraphs, sentences, ... - you are highlighting the first word of the moved text with: \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move First-word \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move ... rest of the moved text.... % MPI-2.1 round-two - end of text-move c) If you want to delete text (i.e. not only a move to another location), the please us \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor Last word of the previous text \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line % the text you delete must be preceded with "% " % deprecated text % ... % deprecated text % MPI-2.1 round-two - end of deteted text Additionally, you must add this outcommented text to the end of removed_source.tex Caution: These macros work only in black parts of the text. In blue parts you must substitute \mpiiidotiMergeNEWforSINGLEendI% by \mpiiidotiMergeNEWforSINGLEendII% The highlighting is done with red color. (There are only a few other sentences from me magenta. Therefore red should be the best to highlight the round-two modifications.) ----------------------------------------------------- Using svn: Before you start to make changes: cd ....your_directory..../trunk/MPI-2.1/ svn update to get the newest sources. After you made changes, please call make and check mpi-report.pdf to guarantee that all your changes are really highlighted with *red* color. When you make the first svn commit after you received a new username with write-permission, you must use the aditional option --username your_new_user_name Please commit with vn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' Please commit as soon as you finished the changes and after you have checked the red color. -------------------------------------------------- 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) From bronis at [hidden] Sat Apr 12 18:04:21 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Sat, 12 Apr 2008 16:04:21 -0700 (PDT) Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: Rolf: Re: > This e-mail is the first preparation of the official reading. > Please read carefully. > > Again,we have a stable and consistent draft. > It is SVN revision 108 and pdf and ps are on > http://www.hlrs.de/mpi/mpi21/doc/ > (username and password are mpi21) > > Nearly all chapters have received an update by the chapters' authors. > Not finished is - as far as I can see > - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > - Datatypes [it was split from Point-to-point] (Rich Graham) > and full MPI-2 based chapters (maybe without need for updates) > - Terms (Tony Skjellum) > - External Interfaces (Bronis de Supinski) As I mentioned, I do not have time this week. > - Profiling (Bronis de Supinski) This was done last week and you checked in the changes. Bronis > Therefore, review can start in all chapters, except the datatype chapter. > > IMPORTANT for authors: > If you make further modifications, please be sure that you use > the macros and that your modification (or at least an delete-anchor) > is printed **red**. (Details on using the macros, see below.) > Please check red color in the resulting mpi-report.pdf before you > svn commit your changes. > As far as I can see, all changes up to now may have no problem > for acceptance by the Forum. > At this late stage, I would recommend to do only changes that do > not need intensive debates at the Forum meeting. Such things > would be MPI-2.2 modifications. > > IMPORTANT for reviewers: > - 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). > - Please make all comments in the format > > ---------------------------------------------------------------------------------- > 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.) > ---------------------------------------------------------------------------------- > > - Please send only review items that are in the category > -- ERROR, must be fixed. > - If you want to send an item in the categories > -- Nice to have, > -- Editorial proposal (like move xxx to yyy), > -- Clarification which needs Forum decisions, > -- ... > then please substitute the __ by 22, because then it should be > handled in MPI-2.2. > > This format is used in > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > where all reviews are filed in. > (I'll substitute your xx by the next number. If you have more than > 26 items, then please continue with xx.a -- xx.z, yy.a - ...) > > Please use this format. I'll have only a few minutes between two flights > to put all reviews together. > > WORKPLAN: > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to MPI-2.2! > - I'm on travel and may not be able to respond on e-mails this week. > - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > final version for all final reviews and for the official reading. > - Version Apr. 17 together with all your review mails will be the > basis for the official reading. > - Reviews until Friday, Apr. 25. according the format above. > - Saturday, Apr. 26: > I will put all reviews together to have unique numbers. > > Best regards > Rolf > > > Annex: The rules for authors: > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > c) If you want to delete text (i.e. not only a move to another location), > the please us > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you must add this outcommented text to the end of > removed_source.tex > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > ----------------------------------------------------- > Using svn: > Before you start to make changes: > > cd ....your_directory..../trunk/MPI-2.1/ > svn update > > to get the newest sources. > > After you made changes, please call make and check mpi-report.pdf > to guarantee that all your changes are really highlighted with *red* color. > > When you make the first svn commit after you received a new username with > write-permission, you must use the aditional option > > --username your_new_user_name > > Please commit with > > svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > > Please commit as soon as you finished the changes and after you have > checked the red color. > > -------------------------------------------------- > > 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 > From rabenseifner at [hidden] Sun Apr 13 02:12:15 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sun, 13 Apr 2008 09:12:15 +0200 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: Bronis, On Sat, 12 Apr 2008 16:04:21 -0700 (PDT) "Bronis R. de Supinski" wrote: > > - External Interfaces (Bronis de Supinski) > > As I mentioned, I do not have time this week. Okay, I will rework the Introduction today. Then it is done. In MPI-2.2, we can move misc-2.tex, the rest of ei-2.tex into other chapters. For MPI-2.1 that's enough what we have reached. 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) From rabenseifner at [hidden] Sun Apr 13 10:28:44 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sun, 13 Apr 2008 17:28:44 +0200 Subject: [Mpi-21] REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: Dear reviewer, if you find a bug, please write also the needed correction in your review. (If the correction is not obvious, it may be a MPI-2.2 problem). Your reviews will be collected and have to go directly into the Forum meeting and must be handled by the Forum. Therefore, please use the format described below. Best regards Rolf On Sun, 13 Apr 2008 00:05:37 +0200 "Rolf Rabenseifner" wrote: > Dear chapter author, dear reviewer, > > This e-mail is the first preparation of the official reading. > Please read carefully. > > Again,we have a stable and consistent draft. > It is SVN revision 108 and pdf and ps are on > http://www.hlrs.de/mpi/mpi21/doc/ > (username and password are mpi21) > > Nearly all chapters have received an update by the chapters' authors. > Not finished is - as far as I can see > - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > - Datatypes [it was split from Point-to-point] (Rich Graham) > and full MPI-2 based chapters (maybe without need for updates) > - Terms (Tony Skjellum) > - External Interfaces (Bronis de Supinski) > - Profiling (Bronis de Supinski) > Therefore, review can start in all chapters, except the datatype chapter. > > IMPORTANT for authors: > If you make further modifications, please be sure that you use > the macros and that your modification (or at least an delete-anchor) > is printed **red**. (Details on using the macros, see below.) > Please check red color in the resulting mpi-report.pdf before you > svn commit your changes. > As far as I can see, all changes up to now may have no problem > for acceptance by the Forum. > At this late stage, I would recommend to do only changes that do > not need intensive debates at the Forum meeting. Such things > would be MPI-2.2 modifications. > > IMPORTANT for reviewers: > - 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). > - Please make all comments in the format > > ---------------------------------------------------------------------------------- > 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.) > ---------------------------------------------------------------------------------- > > - Please send only review items that are in the category > -- ERROR, must be fixed. > - If you want to send an item in the categories > -- Nice to have, > -- Editorial proposal (like move xxx to yyy), > -- Clarification which needs Forum decisions, > -- ... > then please substitute the __ by 22, because then it should be > handled in MPI-2.2. > > This format is used in > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > where all reviews are filed in. > (I'll substitute your xx by the next number. If you have more than > 26 items, then please continue with xx.a -- xx.z, yy.a - ...) > > Please use this format. I'll have only a few minutes between two flights > to put all reviews together. > > WORKPLAN: > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to MPI-2.2! > - I'm on travel and may not be able to respond on e-mails this week. > - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > final version for all final reviews and for the official reading. > - Version Apr. 17 together with all your review mails will be the > basis for the official reading. > - Reviews until Friday, Apr. 25. according the format above. > - Saturday, Apr. 26: > I will put all reviews together to have unique numbers. > > Best regards > Rolf > > > Annex: The rules for authors: > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > c) If you want to delete text (i.e. not only a move to another location), > the please us > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you must add this outcommented text to the end of > removed_source.tex > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > ----------------------------------------------------- > Using svn: > Before you start to make changes: > > cd ....your_directory..../trunk/MPI-2.1/ > svn update > > to get the newest sources. > > After you made changes, please call make and check mpi-report.pdf > to guarantee that all your changes are really highlighted with *red* color. > > When you make the first svn commit after you received a new username with > write-permission, you must use the aditional option > > --username your_new_user_name > > Please commit with > > svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > > Please commit as soon as you finished the changes and after you have > checked the red color. > > -------------------------------------------------- > > 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 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) From htor at [hidden] Sun Apr 13 13:35:51 2008 From: htor at [hidden] (Torsten Hoefler) Date: Sun, 13 Apr 2008 14:35:51 -0400 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: <20080413183551.GS9521@benten.cs.indiana.edu> 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 EDIT p129.19-41 "all group members" vs. "all members of a group" should use the same phrasing (parallel structure) 5.b NICE p129.41 Reference to 5.11 not 5.11.1 5.c EDIT p129.45 remove "," (comma) 5.d EDIT p129.43 replace "the same" with "a" 5.e EDIT p129.45 "the same group" in line 43 conflicts with "group or groups" 5.f CLAR p131.1 add "with exceptions stated in the following" to first sentence 5.g EDIT p131.4 no linebreak (Chapter~\ref{...}) 5.h ERR p131.31 replace "will" with "might" 5.i 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) 5.j 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) 5.k EDIT p133.32 "a" -> "an"? 5.l 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 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?) 5.o EDIT p136.32 move sentence to end of the previous paragraph (line 25) 5.p EDIT p136.37 "data is braodcasted" (not braodcast) 5.q 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) 5.s EDIT p138.3 write "all processes" instead of "process i" (i is never defined) 5.t 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?)? 5.u 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) 5.w EDIT p157.35 why a separate subsection for Alltoallw but not for Alltoallv? I'd remove this subsection 5.x EDIT p157.36 the first two sentences should go to rationale (we don't need to rationalize the operation in the description) 5.y EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for MPI_Reduce" 5.z EDIT p162.13 state that the example is in Fortran (it's said for all the C examples before) 5.aa 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. 5.ab CLAR p163.20 replace "bit" by "numeric" or "integer" 5.ac EDIT p167.41 doubled sentence "The order of ..." 5.ad CLAR p169.2 add: (without supporting the "in place" option) 5.ae ERR p169.16-20 the example will deadlock if root == groupsize-1. Has been there for a while :). Use Irecv/Wait instead. 5.af EDIT p171.48 state that example is in Fortran 5.ag ERR p174.12-20 this rationale should be erased completely because it explains (for MPI-1), why only the inclusive is supported ;-) 5.ah 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) 5.ak CLAR p179.27 maybe we should add: "and to ensure appropriate matching (for deterministic behavior) 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 From htor at [hidden] Sun Apr 13 13:42:56 2008 From: htor at [hidden] (Torsten Hoefler) Date: Sun, 13 Apr 2008 14:42:56 -0400 Subject: [Mpi-21] REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: <20080413184256.GT9521@benten.cs.indiana.edu> Rolf, > if you find a bug, please write also the needed correction > in your review. done > Your reviews will be collected and have to go directly into the Forum > meeting and must be handled by the Forum. > Therefore, please use the format described below. oh, I did not know this before sending my review. I would not recommend to feed the results of my review directly to the forum because many things are small typos or minor editing comments that would be a waste of time for the whole forum. So we might want to filter my review or just apply the smaller changes in collaboration with the chapter author before presenting it to the forum. 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 From bronis at [hidden] Sun Apr 13 13:58:27 2008 From: bronis at [hidden] (Bronis R. de Supinski) Date: Sun, 13 Apr 2008 11:58:27 -0700 (PDT) Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: <20080413183551.GS9521@benten.cs.indiana.edu> Message-ID: Torsten, Adam and Rolf: Re: > 5.p EDIT p136.37 "data is braodcasted" (not braodcast) This is not correct. The preferred spelling for the past tense of "broadcast" is "broadcast" ("broadcasted" is an acceptable alternative but I don't see why we would want to switch to it). Bronis From htor at [hidden] Sun Apr 13 14:10:02 2008 From: htor at [hidden] (Torsten Hoefler) Date: Sun, 13 Apr 2008 15:10:02 -0400 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: Message-ID: <20080413191002.GU9521@benten.cs.indiana.edu> Bronis, > Re: > > 5.p EDIT p136.37 "data is braodcasted" (not braodcast) > > This is not correct. The preferred spelling for the past tense > of "broadcast" is "broadcast" ("broadcasted" is an acceptable > alternative but I don't see why we would want to switch to it). ok, I agree - didn't know this! So this clearly is one of the items to discard (there might be more). Thanks, 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 From rabenseifner at [hidden] Mon Apr 14 01:45:45 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Mon, 14 Apr 2008 08:45:45 +0200 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: <20080413183551.GS9521@benten.cs.indiana.edu> Message-ID: All authors, Adam and Torsten, all authors have their write-token to their chapter. This week, they still should correct small things and should switch the __ in the form to DON2. On Friday 18, I'll take back the write-token witout any further announcment and will produce the final version of MPI-2.1 that will go into "official reading". I.e., until this Thursday, April 17, all **authors** should fix what they can and what reviewers report. I will not fix any further bug. The responsibility is at the chapters authors. Best regards Rolf On Sun, 13 Apr 2008 14:35:51 -0400 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 EDIT p129.19-41 "all group members" vs. "all members of a group" > should use the same phrasing (parallel structure) > 5.b NICE p129.41 Reference to 5.11 not 5.11.1 > 5.c EDIT p129.45 remove "," (comma) > 5.d EDIT p129.43 replace "the same" with "a" > 5.e EDIT p129.45 "the same group" in line 43 conflicts with "group or > groups" > 5.f CLAR p131.1 add "with exceptions stated in the following" to first > sentence > 5.g EDIT p131.4 no linebreak (Chapter~\ref{...}) > 5.h ERR p131.31 replace "will" with "might" > 5.i 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) > 5.j 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) > 5.k EDIT p133.32 "a" -> "an"? > 5.l 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 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?) > 5.o EDIT p136.32 move sentence to end of the previous paragraph (line > 25) > 5.p EDIT p136.37 "data is braodcasted" (not braodcast) > 5.q 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) > 5.s EDIT p138.3 write "all processes" instead of "process i" (i is > never defined) > 5.t 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?)? > 5.u 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) > 5.w EDIT p157.35 why a separate subsection for Alltoallw but not for > Alltoallv? I'd remove this subsection > 5.x EDIT p157.36 the first two sentences should go to rationale (we > don't need to rationalize the operation in the > description) > 5.y EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for > MPI_Reduce" > 5.z EDIT p162.13 state that the example is in Fortran (it's said for > all the C examples before) > 5.aa 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. > 5.ab CLAR p163.20 replace "bit" by "numeric" or "integer" > 5.ac EDIT p167.41 doubled sentence "The order of ..." > 5.ad CLAR p169.2 add: (without supporting the "in place" option) > 5.ae ERR p169.16-20 the example will deadlock if root == groupsize-1. Has > been there for a while :). Use Irecv/Wait instead. > 5.af EDIT p171.48 state that example is in Fortran > 5.ag ERR p174.12-20 this rationale should be erased completely because it > explains (for MPI-1), why only the inclusive is supported ;-) > 5.ah 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) > 5.ak CLAR p179.27 maybe we should add: "and to ensure appropriate > matching (for deterministic behavior) > > 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 > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 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) From moody20 at [hidden] Mon Apr 14 11:53:29 2008 From: moody20 at [hidden] (Adam Moody) Date: Mon, 14 Apr 2008 09:53:29 -0700 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you In-Reply-To: Message-ID: <48038C09.8010802@llnl.gov> Hi Rolf, Yes, those changes are fine by me. Thanks, -Adam Rolf Rabenseifner wrote: >Hi Adam, > >this is really a good merge that you have done. >Good ideas and very carefully implemented. > >The reviewers can see (nearly) all of your modifications in red. >I expect that your reviewersand the Forum will enjoy your modifications. > >I have restored two minor mods you have done: >(Line numbers refer to the new file you'll get with svn update) > >coll.tex, line 412 - I restored the "intracommunicator" > because the categories describe the behavior only on > intracommunicators, not on all, e.g., ALLGATHER has > one result on intra and two on inter and the wording is > "the result". > >coll.tex, line 491 - restored the word "also". > These routines are valid for intra and inter. > Writing "apply to inter" may be interpreted that they are > only valid for inter. > Writing "also apply to inter" should solve this problem. > I also colored this sentence red. > >I hop, this isokay with you. > >Best regards >Rolf > > >On Fri, 11 Apr 2008 15:22:10 -0700 > Adam Moody wrote: > > >>Hi Rolf, >>I have checked in my changes for the Collectives chapter. It's ready to >>be reviewed by the collective chapter reviewers. >>-Adam >> >>Rolf Rabenseifner wrote: >> >> >> >>>>>write-token again to the chapter authors << >>>>>- but only until Saturday 8:00 European GMT << >>>>> >>>>> >>>>> >>>>> >>>Hi all authors and reviewers, >>> >>>Please read this mail carfully, if you want to make any further >>>modification of the text. >>> >>>You must now call >>> svn update >>>to get the newest release!! >>>We have a again a consistent version. Nearly all of >>> >>> http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >>> >>>is now implemented in the tex-source. >>>Only a few items are still open, see statistics at the beginning. >>> >>>You can view the current version (it is svn revision 92) at >>> >>> http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf >>> >>>It is only today and Friday remaining for finishing MPI-2.1. >>>I give back the write-token to the authors. >>> >>>On Saturday morning European time, I take the write-token >>>automatically on Saturday morning to build final pdf for the >>>reviews. >>> >>>As I can see, many chapter authors made fine cleaning to the text. >>>All larger changes should be defered to MPI-2.2! >>>Especially the merge of MPI Environment (inquiry.tex), Misc (misc-2.tex) >>>and External Interfaces (ei-2.tex) >>>to one chapter "MPI Environment and Miscellany" (with 45 pages) >>>may be defered also to MPI-2.2. >>> >>>Up to now, I was able to check most changes and they look fine. >>> >>>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.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 >> >> > > > >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 > > > From dgregor at [hidden] Wed Apr 16 16:43:19 2008 From: dgregor at [hidden] (Doug Gregor) Date: Wed, 16 Apr 2008 17:43:19 -0400 Subject: [Mpi-21] Relevance of C++ MPI binding of www.boost.org In-Reply-To: Message-ID: <04D2365C-03F1-484C-B307-1DC65AEBDD15@osl.iu.edu> On Apr 3, 2008, at 12:09 PM, Rolf Rabenseifner wrote: > which relevance has the MPI C++ binding of Boost ( http://www.boost.org/ > )? > In the actual version 1.35 > http://www.boost.org/users/news/version_1_35_0 > one can find a "C++-friendly interface to the standard Message > Passing Interface". > > The comment from boost: > "Although there exist C++ bindings for MPI, they offer little > functionality over the C bindings." > > Is there any knowledge of whether in real C++ programming, whether > the official C++ MPI binding or the C++ boost MPI binding is > more often used in the C++ community? Boost's C++ bindings have only been in an official Boost release for a few weeks, so there's no way that the user base is even a fraction of the user base of the official C++ bindings. As such, these bindings would certainly not be ready for standardization. And, as Jeff said, the MPI forum has already rejected "richer" object- oriented C++ bindings in favor of what we have now. I don't see any indication that this is going to change, and I don't think it should. We should not spend our time discussing bindings (or improved bindings) for every language out there. Rather, we should spend our time making sure that such bindings *can* be built on top of MPI's C or Fortran bindings. MPI is good at message passing, Python is good at being Python. - Doug From thakur at [hidden] Wed Apr 16 16:57:28 2008 From: thakur at [hidden] (Rajeev Thakur) Date: Wed, 16 Apr 2008 16:57:28 -0500 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you In-Reply-To: Message-ID: <00eb01c8a00c$dcc5ee70$860add8c@mcs.anl.gov> Adam, You have done a wonderful job of fixing the merged collectives chapter, which was a nontrivial task (and hence I didn't volunteer for it :-)). I only have some minor comments listed below. Rajeev * pg 133, ln 27-28: change to the plural -- "patterns of" and "do not fit" * pg 134, ln 32-33: What does matching arguments mean? Does it mean same arguments? That's not true for the root argument of rooted collectives on the group containing the root. Maybe just delete the sentence. * pg 136, ln 22-23: move "for intracommunicators" to the beginning of the sentence * pg 140, ln 28: change "are using" to "use" * pg 149, ln 45: change "are using" to "use" * pg 154, ln 33: change "are using" to "use" * pg 162, ln 10: change "are using" to "use" * pg 163, Sec 5.9.3: Delete the sentence "This is an extension to MPI-1.2, ..." since we are all one now. Merge the next paragraph on heterogeneous into this one, and fix spelling of "charater" to character. * pg 165, ln 10: change "are using" to "use" * pg 167, ln 38-39: Question - Do we want to also list MPI_Accumulate with a forward reference to it? * pg 170, ln 3: change "is using" to "uses" * pg 171, ln 38: should be "In such a case" or better "In this case" * pg 171, ln 43: change "is using" to "uses" and "an intracommunicators" to the singular * pg 174, ln 11: change "illegal" to "invalid" * pg 174, ln 12-20: Delete the entire rationale. It was included in MPI-1 to justify not having an exclusive scan. Doesn't apply any more. You deleted only the last sentence, which was explicit, but the whole rationale should go. * pg 175, ln 13-20: By the same token, delete the entire rationale here. It was used to justify adding an exclusive scan to MPI-2. Even the "no in-place version" is covered above in lin 5. Maybe you can change that line 5 to include the justification as follows: "No in-place version is supported because it is not clear what this means for the process with rank zero". Note that it should be "process with rank zero" rather than "process for rank zero" as in the current text. * pg 175, ln 25: change "is using" to "uses" Rest looks great! > -----Original Message----- > From: mpi-21-bounces_at_[hidden] > [mailto:mpi-21-bounces_at_[hidden]] On Behalf Of Rolf > Rabenseifner > Sent: Saturday, April 12, 2008 10:15 AM > To: MPI 2.1 Mailing List > Subject: Re: [Mpi-21] AUTHORS: new consistent version and > write-token to you > > Hi Adam, > > this is really a good merge that you have done. > Good ideas and very carefully implemented. > > The reviewers can see (nearly) all of your modifications in red. > I expect that your reviewersand the Forum will enjoy your > modifications. > > I have restored two minor mods you have done: > (Line numbers refer to the new file you'll get with svn update) > > coll.tex, line 412 - I restored the "intracommunicator" > because the categories describe the behavior only on > intracommunicators, not on all, e.g., ALLGATHER has > one result on intra and two on inter and the wording is > "the result". > > coll.tex, line 491 - restored the word "also". > These routines are valid for intra and inter. > Writing "apply to inter" may be interpreted that they are > only valid for inter. > Writing "also apply to inter" should solve this problem. > I also colored this sentence red. > > I hop, this isokay with you. > > Best regards > Rolf > > > On Fri, 11 Apr 2008 15:22:10 -0700 > Adam Moody wrote: > > Hi Rolf, > > I have checked in my changes for the Collectives chapter. > It's ready to > > be reviewed by the collective chapter reviewers. > > -Adam > > > > Rolf Rabenseifner wrote: > > > > >>>write-token again to the chapter authors << > > >>>- but only until Saturday 8:00 European GMT << > > >>> > > >>> > > > > > >Hi all authors and reviewers, > > > > > >Please read this mail carfully, if you want to make any further > > >modification of the text. > > > > > >You must now call > > > svn update > > >to get the newest release!! > > >We have a again a consistent version. Nearly all of > > > > > > > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > > > > > >is now implemented in the tex-source. > > >Only a few items are still open, see statistics at the beginning. > > > > > >You can view the current version (it is svn revision 92) at > > > > > > http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf > > > > > >It is only today and Friday remaining for finishing MPI-2.1. > > >I give back the write-token to the authors. > > > > > >On Saturday morning European time, I take the write-token > > >automatically on Saturday morning to build final pdf for the > > >reviews. > > > > > >As I can see, many chapter authors made fine cleaning to the text. > > >All larger changes should be defered to MPI-2.2! > > >Especially the merge of MPI Environment (inquiry.tex), > Misc (misc-2.tex) > > >and External Interfaces (ei-2.tex) > > >to one chapter "MPI Environment and Miscellany" (with 45 pages) > > >may be defered also to MPI-2.2. > > > > > >Up to now, I was able to check most changes and they look fine. > > > > > >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.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 > > > > 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 > > From moody20 at [hidden] Wed Apr 16 20:32:59 2008 From: moody20 at [hidden] (Adam Moody) Date: Wed, 16 Apr 2008 18:32:59 -0700 Subject: [Mpi-21] AUTHORS: new consistent version and write-token to you In-Reply-To: <00eb01c8a00c$dcc5ee70$860add8c@mcs.anl.gov> Message-ID: <4806A8CB.1040203@llnl.gov> Hi Rajeev, Thanks for all of your feedback. I've made every change but two, which I think we should delay to a decision for the Forum (or at least wait to get more votes from reviewers). Rolf, Can you add the following items to some ballot to be considered by the Forum? * pg 134, ln 32-33: What does matching arguments mean? Does it mean same arguments? That's not true for the root argument of rooted collectives on the group containing the root. Maybe just delete the sentence. * pg 163, Sec 5.9.3: Delete the sentence "This is an extension to MPI-1.2, ..." since we are all one now. I've incorporated the rest of the edits Rajeev suggested and committed the new chapter. -Adam Rajeev Thakur wrote: >Adam, > You have done a wonderful job of fixing the merged collectives chapter, >which was a nontrivial task (and hence I didn't volunteer for it :-)). I >only have some minor comments listed below. > >Rajeev > > >* pg 133, ln 27-28: change to the plural -- "patterns of" and "do not fit" > > Done. >* pg 134, ln 32-33: What does matching arguments mean? Does it mean same >arguments? That's not true for the root argument of rooted collectives on >the group containing the root. Maybe just delete the sentence. > > Yes, I agree, but it's not clear to me how to clarify this point either. There's probably a clean way to explain the intent here, but I don't want to make that decision. I'll leave this in to get more input from the Forum. >* pg 136, ln 22-23: move "for intracommunicators" to the beginning of the >sentence > > Done. >* pg 140, ln 28: change "are using" to "use" > > Done. >* pg 149, ln 45: change "are using" to "use" > > Done. >* pg 154, ln 33: change "are using" to "use" > > Done. >* pg 162, ln 10: change "are using" to "use" > > Done. >* pg 163, Sec 5.9.3: Delete the sentence "This is an extension to MPI-1.2, >..." since we are all one now. Merge the next paragraph on heterogeneous >into this one, and fix spelling of "charater" to character. > > I fixed the "charater" mis-spelling and merged the paragraphs. I left the statement about MPI-1.2 for now, although I moved it so that, after merging the other paragraph, the resulting paragraph reads a little more smoothly. This statement seems to highlight an important, but subtle change. I want to get feedback from the Forum on this item. >* pg 165, ln 10: change "are using" to "use" > > Done. >* pg 167, ln 38-39: Question - Do we want to also list MPI_Accumulate with a >forward reference to it? > >* pg 170, ln 3: change "is using" to "uses" > > Done. >* pg 171, ln 38: should be "In such a case" or better "In this case" > > Done. >* pg 171, ln 43: change "is using" to "uses" and "an intracommunicators" to >the singular > > Done. >* pg 174, ln 11: change "illegal" to "invalid" > > Done. >* pg 174, ln 12-20: Delete the entire rationale. It was included in MPI-1 to >justify not having an exclusive scan. Doesn't apply any more. You deleted >only the last sentence, which was explicit, but the whole rationale should >go. > > Done. >* pg 175, ln 13-20: By the same token, delete the entire rationale here. It >was used to justify adding an exclusive scan to MPI-2. Even the "no in-place >version" is covered above in lin 5. Maybe you can change that line 5 to >include the justification as follows: "No in-place version is supported >because it is not clear what this means for the process with rank zero". >Note that it should be "process with rank zero" rather than "process for >rank zero" as in the current text. > > I kept the rationale, because I think it provides some useful information here, but I changed it to the following: The exclusive scan is more general than the inclusive scan. Any inclusive scan operation can be achieved by using the exclusive scan and then locally combining the local contribution. Note that for non-invertable operations such as MPI_MAX, the exclusive scan cannot be computed with the inclusive scan. No in-place version is specified for MPI_EXSCAN because it is not clear what this means for the process with rank zero. >* pg 175, ln 25: change "is using" to "uses" > > Done. >Rest looks great! > > > > > > > >>-----Original Message----- >>From: mpi-21-bounces_at_[hidden] >>[mailto:mpi-21-bounces_at_[hidden]] On Behalf Of Rolf >>Rabenseifner >>Sent: Saturday, April 12, 2008 10:15 AM >>To: MPI 2.1 Mailing List >>Subject: Re: [Mpi-21] AUTHORS: new consistent version and >>write-token to you >> >>Hi Adam, >> >>this is really a good merge that you have done. >>Good ideas and very carefully implemented. >> >>The reviewers can see (nearly) all of your modifications in red. >>I expect that your reviewersand the Forum will enjoy your >>modifications. >> >>I have restored two minor mods you have done: >>(Line numbers refer to the new file you'll get with svn update) >> >>coll.tex, line 412 - I restored the "intracommunicator" >> because the categories describe the behavior only on >> intracommunicators, not on all, e.g., ALLGATHER has >> one result on intra and two on inter and the wording is >> "the result". >> >>coll.tex, line 491 - restored the word "also". >> These routines are valid for intra and inter. >> Writing "apply to inter" may be interpreted that they are >> only valid for inter. >> Writing "also apply to inter" should solve this problem. >> I also colored this sentence red. >> >>I hop, this isokay with you. >> >>Best regards >>Rolf >> >> >>On Fri, 11 Apr 2008 15:22:10 -0700 >> Adam Moody wrote: >> >> >>>Hi Rolf, >>>I have checked in my changes for the Collectives chapter. >>> >>> >>It's ready to >> >> >>>be reviewed by the collective chapter reviewers. >>>-Adam >>> >>>Rolf Rabenseifner wrote: >>> >>> >>> >>>>>>write-token again to the chapter authors << >>>>>>- but only until Saturday 8:00 European GMT << >>>>>> >>>>>> >>>>>> >>>>>> >>>>Hi all authors and reviewers, >>>> >>>>Please read this mail carfully, if you want to make any further >>>>modification of the text. >>>> >>>>You must now call >>>> svn update >>>>to get the newest release!! >>>>We have a again a consistent version. Nearly all of >>>> >>>> >>>> >>>> >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >> >> >>>>is now implemented in the tex-source. >>>>Only a few items are still open, see statistics at the beginning. >>>> >>>>You can view the current version (it is svn revision 92) at >>>> >>>> http://www.hlrs.de/mpi/mpi21/doc/mpi-report.pdf >>>> >>>>It is only today and Friday remaining for finishing MPI-2.1. >>>>I give back the write-token to the authors. >>>> >>>>On Saturday morning European time, I take the write-token >>>>automatically on Saturday morning to build final pdf for the >>>>reviews. >>>> >>>>As I can see, many chapter authors made fine cleaning to the text. >>>>All larger changes should be defered to MPI-2.2! >>>>Especially the merge of MPI Environment (inquiry.tex), >>>> >>>> >>Misc (misc-2.tex) >> >> >>>>and External Interfaces (ei-2.tex) >>>>to one chapter "MPI Environment and Miscellany" (with 45 pages) >>>>may be defered also to MPI-2.2. >>>> >>>>Up to now, I was able to check most changes and they look fine. >>>> >>>>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.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 >>> >>> >> >>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 > > > From rabenseifner at [hidden] Thu Apr 17 07:32:29 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Thu, 17 Apr 2008 14:32:29 +0200 Subject: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: Message-ID: All authors (except Rich [pt2pt and datatypes]), - The authors get back the write-token until Thursday, Apr. 17. (If you need also Friday Apr. 18, then please inform me!!) - All stuff that is not done until that point, will be defered to MPI-2.2! This is the last reminder and chance for latest updates **today**. (Details on the WORKPLAN, see mail below) Best regards Rolf On Sun, 13 Apr 2008 00:05:37 +0200 "Rolf Rabenseifner" wrote: > Dear chapter author, dear reviewer, > > This e-mail is the first preparation of the official reading. > Please read carefully. > > Again,we have a stable and consistent draft. > It is SVN revision 108 and pdf and ps are on > http://www.hlrs.de/mpi/mpi21/doc/ > (username and password are mpi21) > > Nearly all chapters have received an update by the chapters' authors. > Not finished is - as far as I can see > - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > - Datatypes [it was split from Point-to-point] (Rich Graham) > and full MPI-2 based chapters (maybe without need for updates) > - Terms (Tony Skjellum) > - External Interfaces (Bronis de Supinski) > - Profiling (Bronis de Supinski) > Therefore, review can start in all chapters, except the datatype chapter. > > IMPORTANT for authors: > If you make further modifications, please be sure that you use > the macros and that your modification (or at least an delete-anchor) > is printed **red**. (Details on using the macros, see below.) > Please check red color in the resulting mpi-report.pdf before you > svn commit your changes. > As far as I can see, all changes up to now may have no problem > for acceptance by the Forum. > At this late stage, I would recommend to do only changes that do > not need intensive debates at the Forum meeting. Such things > would be MPI-2.2 modifications. > > IMPORTANT for reviewers: > - 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). > - Please make all comments in the format > > ---------------------------------------------------------------------------------- > 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.) > ---------------------------------------------------------------------------------- > > - Please send only review items that are in the category > -- ERROR, must be fixed. > - If you want to send an item in the categories > -- Nice to have, > -- Editorial proposal (like move xxx to yyy), > -- Clarification which needs Forum decisions, > -- ... > then please substitute the __ by 22, because then it should be > handled in MPI-2.2. > > This format is used in > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > where all reviews are filed in. > (I'll substitute your xx by the next number. If you have more than > 26 items, then please continue with xx.a -- xx.z, yy.a - ...) > > Please use this format. I'll have only a few minutes between two flights > to put all reviews together. > > WORKPLAN: > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to MPI-2.2! > - I'm on travel and may not be able to respond on e-mails this week. > - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > final version for all final reviews and for the official reading. > - Version Apr. 17 together with all your review mails will be the > basis for the official reading. > - Reviews until Friday, Apr. 25. according the format above. > - Saturday, Apr. 26: > I will put all reviews together to have unique numbers. > > Best regards > Rolf > > > Annex: The rules for authors: > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > c) If you want to delete text (i.e. not only a move to another location), > the please us > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you must add this outcommented text to the end of > removed_source.tex > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > ----------------------------------------------------- > Using svn: > Before you start to make changes: > > cd ....your_directory..../trunk/MPI-2.1/ > svn update > > to get the newest sources. > > After you made changes, please call make and check mpi-report.pdf > to guarantee that all your changes are really highlighted with *red* color. > > When you make the first svn commit after you received a new username with > write-permission, you must use the aditional option > > --username your_new_user_name > > Please commit with > > svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > > Please commit as soon as you finished the changes and after you have > checked the red color. > > -------------------------------------------------- > > 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) 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) From jsquyres at [hidden] Thu Apr 17 07:41:25 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Thu, 17 Apr 2008 08:41:25 -0400 Subject: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: Message-ID: I believe that the language bindings chapter is up-to-date for MPI 2.1. On Apr 17, 2008, at 8:32 AM, Rolf Rabenseifner wrote: > All authors (except Rich [pt2pt and datatypes]), > > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to > MPI-2.2! > > This is the last reminder and chance for latest updates **today**. > > (Details on the WORKPLAN, see mail below) > > Best regards > Rolf > > > On Sun, 13 Apr 2008 00:05:37 +0200 > "Rolf Rabenseifner" wrote: >> Dear chapter author, dear reviewer, >> >> This e-mail is the first preparation of the official reading. >> Please read carefully. >> >> Again,we have a stable and consistent draft. >> It is SVN revision 108 and pdf and ps are on >> http://www.hlrs.de/mpi/mpi21/doc/ >> (username and password are mpi21) >> >> Nearly all chapters have received an update by the chapters' authors. >> Not finished is - as far as I can see >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) >> - Datatypes [it was split from Point-to-point] (Rich Graham) >> and full MPI-2 based chapters (maybe without need for updates) >> - Terms (Tony Skjellum) >> - External Interfaces (Bronis de Supinski) >> - Profiling (Bronis de Supinski) >> Therefore, review can start in all chapters, except the datatype >> chapter. >> >> IMPORTANT for authors: >> If you make further modifications, please be sure that you use >> the macros and that your modification (or at least an delete-anchor) >> is printed **red**. (Details on using the macros, see below.) >> Please check red color in the resulting mpi-report.pdf before you >> svn commit your changes. >> As far as I can see, all changes up to now may have no problem >> for acceptance by the Forum. >> At this late stage, I would recommend to do only changes that do >> not need intensive debates at the Forum meeting. Such things >> would be MPI-2.2 modifications. >> >> IMPORTANT for reviewers: >> - 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). >> - Please make all comments in the format >> >> ---------------------------------------------------------------------------------- >> 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.) >> ---------------------------------------------------------------------------------- >> >> - Please send only review items that are in the category >> -- ERROR, must be fixed. >> - If you want to send an item in the categories >> -- Nice to have, >> -- Editorial proposal (like move xxx to yyy), >> -- Clarification which needs Forum decisions, >> -- ... >> then please substitute the __ by 22, because then it should be >> handled in MPI-2.2. >> >> This format is used in >> http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >> where all reviews are filed in. >> (I'll substitute your xx by the next number. If you have more than >> 26 items, then please continue with xx.a -- xx.z, yy.a - ...) >> >> Please use this format. I'll have only a few minutes between two >> flights >> to put all reviews together. >> >> WORKPLAN: >> - The authors get back the write-token until Thursday, Apr. 17. >> (If you need also Friday Apr. 18, then please inform me!!) >> - All stuff that is not done until that point, will be defered to >> MPI-2.2! >> - I'm on travel and may not be able to respond on e-mails this week. >> - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the >> final version for all final reviews and for the official reading. >> - Version Apr. 17 together with all your review mails will be the >> basis for the official reading. >> - Reviews until Friday, Apr. 25. according the format above. >> - Saturday, Apr. 26: >> I will put all reviews together to have unique numbers. >> >> Best regards >> Rolf >> >> >> Annex: The rules for authors: >> >> The goals of your work as chapter author: >> ----------------------------------------- >> >> - Remove references to MPI-1 and MPI-2. >> - Substitute by MPI. >> - Necessary modifications to achieve this goal. >> >> With this, we should have a single MPI-2.1 standard that does >> not "know" the MPI-1 or MPI-2 history of individual functions. >> >> ** This should be mainly a task in the area of chapter-introductions. >> ** Please, never change the wording of function definitions. >> >> Exceptions: >> - There are routines that are deprecated and that are >> already referenced in a consistent way. >> My recommendation: >> Current wording: >> There are *new* function, and existing are now deprecated. >> Proposal: >> There are functions, and there exist also deprecated functions >> with (nearly) same functionality but deprecated due to some lack >> in the bindings (or functionality) >> - There is history information in the frontmatter. >> - there is a change-log annex with limited memory (only previous >> version) >> >> Technical editing rule: >> ----------------------- >> >> You must identify all of your changes: >> >> a) new/modified wording - you are highlighting your new/modified >> wording with: >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >> modification >> .... your modified / new wording .... >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of >> modification >> >> b) Moved paragraphs, sentences, ... - you are highlighting the >> first word >> of the moved text with: >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text- >> move >> First-word >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text- >> move >> ... rest of the moved text.... >> % MPI-2.1 round-two - end of text-move >> >> c) If you want to delete text (i.e. not only a move to another >> location), >> the please us >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text- >> anchor >> Last word of the previous text >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor >> >> % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 >> page/line-page/line >> % the text you delete must be preceded with "% " >> % deprecated text >> % ... >> % deprecated text >> % MPI-2.1 round-two - end of deteted text >> >> Additionally, you must add this outcommented text to the end of >> removed_source.tex >> >> Caution: These macros work only in black parts of the text. >> >> In blue parts you must substitute >> \mpiiidotiMergeNEWforSINGLEendI% >> by >> \mpiiidotiMergeNEWforSINGLEendII% >> >> >> The highlighting is done with red color. >> (There are only a few other sentences from me magenta. >> Therefore red should be the best to highlight the round-two >> modifications.) >> >> ----------------------------------------------------- >> Using svn: >> Before you start to make changes: >> >> cd ....your_directory..../trunk/MPI-2.1/ >> svn update >> >> to get the newest sources. >> >> After you made changes, please call make and check mpi-report.pdf >> to guarantee that all your changes are really highlighted with >> *red* color. >> >> When you make the first svn commit after you received a new >> username with >> write-permission, you must use the aditional option >> >> --username your_new_user_name >> >> Please commit with >> >> svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you >> have done' >> >> Please commit as soon as you finished the changes and after you have >> checked the red color. >> >> -------------------------------------------------- >> >> 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) > > > > 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 -- Jeff Squyres Cisco Systems From treumann at [hidden] Thu Apr 17 07:54:50 2008 From: treumann at [hidden] (Richard Treumann) Date: Thu, 17 Apr 2008 08:54:50 -0400 Subject: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: Message-ID: I do not plan to revise Chapter 5 this pass. You have the write token Rolf. Anything not covered in the version I checked in a week or so back should go to MPI 2.2 Dick 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 * -------------- next part -------------- An HTML attachment was scrubbed... URL: From moody20 at [hidden] Thu Apr 17 20:01:18 2008 From: moody20 at [hidden] (Adam Moody) Date: Thu, 17 Apr 2008 18:01:18 -0700 Subject: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: Message-ID: <4807F2DE.5020300@llnl.gov> Hi Rolf, I'll need Friday the 18th to incorporate Torsten's comments into the Collectives chapter. I missed them when he first sent them. -Adam Rolf Rabenseifner wrote: >All authors (except Rich [pt2pt and datatypes]), > >- The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) >- All stuff that is not done until that point, will be defered to MPI-2.2! > >This is the last reminder and chance for latest updates **today**. > >(Details on the WORKPLAN, see mail below) > >Best regards >Rolf > > >On Sun, 13 Apr 2008 00:05:37 +0200 > "Rolf Rabenseifner" wrote: > > >>Dear chapter author, dear reviewer, >> >>This e-mail is the first preparation of the official reading. >>Please read carefully. >> >>Again,we have a stable and consistent draft. >>It is SVN revision 108 and pdf and ps are on >> http://www.hlrs.de/mpi/mpi21/doc/ >>(username and password are mpi21) >> >>Nearly all chapters have received an update by the chapters' authors. >>Not finished is - as far as I can see >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) >> - Datatypes [it was split from Point-to-point] (Rich Graham) >>and full MPI-2 based chapters (maybe without need for updates) >> - Terms (Tony Skjellum) >> - External Interfaces (Bronis de Supinski) >> - Profiling (Bronis de Supinski) >>Therefore, review can start in all chapters, except the datatype chapter. >> >>IMPORTANT for authors: >>If you make further modifications, please be sure that you use >>the macros and that your modification (or at least an delete-anchor) >>is printed **red**. (Details on using the macros, see below.) >>Please check red color in the resulting mpi-report.pdf before you >>svn commit your changes. >>As far as I can see, all changes up to now may have no problem >>for acceptance by the Forum. >>At this late stage, I would recommend to do only changes that do >>not need intensive debates at the Forum meeting. Such things >>would be MPI-2.2 modifications. >> >>IMPORTANT for reviewers: >>- 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). >>- Please make all comments in the format >> >>---------------------------------------------------------------------------------- >>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.) >>---------------------------------------------------------------------------------- >> >>- Please send only review items that are in the category >> -- ERROR, must be fixed. >>- If you want to send an item in the categories >> -- Nice to have, >> -- Editorial proposal (like move xxx to yyy), >> -- Clarification which needs Forum decisions, >> -- ... >> then please substitute the __ by 22, because then it should be >> handled in MPI-2.2. >> >>This format is used in >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >>where all reviews are filed in. >>(I'll substitute your xx by the next number. If you have more than >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) >> >>Please use this format. I'll have only a few minutes between two flights >>to put all reviews together. >> >>WORKPLAN: >>- The authors get back the write-token until Thursday, Apr. 17. >> (If you need also Friday Apr. 18, then please inform me!!) >>- All stuff that is not done until that point, will be defered to MPI-2.2! >>- I'm on travel and may not be able to respond on e-mails this week. >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the >> final version for all final reviews and for the official reading. >>- Version Apr. 17 together with all your review mails will be the >> basis for the official reading. >>- Reviews until Friday, Apr. 25. according the format above. >>- Saturday, Apr. 26: >> I will put all reviews together to have unique numbers. >> >>Best regards >>Rolf >> >> >>Annex: The rules for authors: >> >>The goals of your work as chapter author: >>----------------------------------------- >> >>- Remove references to MPI-1 and MPI-2. >>- Substitute by MPI. >>- Necessary modifications to achieve this goal. >> >>With this, we should have a single MPI-2.1 standard that does >>not "know" the MPI-1 or MPI-2 history of individual functions. >> >>** This should be mainly a task in the area of chapter-introductions. >>** Please, never change the wording of function definitions. >> >>Exceptions: >>- There are routines that are deprecated and that are >> already referenced in a consistent way. >> My recommendation: >> Current wording: >> There are *new* function, and existing are now deprecated. >> Proposal: >> There are functions, and there exist also deprecated functions >> with (nearly) same functionality but deprecated due to some lack >> in the bindings (or functionality) >>- There is history information in the frontmatter. >>- there is a change-log annex with limited memory (only previous version) >> >>Technical editing rule: >>----------------------- >> >>You must identify all of your changes: >> >>a) new/modified wording - you are highlighting your new/modified wording with: >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification >>.... your modified / new wording .... >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification >> >>b) Moved paragraphs, sentences, ... - you are highlighting the first word >> of the moved text with: >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move >>First-word >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move >>... rest of the moved text.... >>% MPI-2.1 round-two - end of text-move >> >>c) If you want to delete text (i.e. not only a move to another location), >> the please us >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor >>Last word of the previous text >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor >> >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line >>% the text you delete must be preceded with "% " >>% deprecated text >>% ... >>% deprecated text >>% MPI-2.1 round-two - end of deteted text >> >> Additionally, you must add this outcommented text to the end of >> removed_source.tex >> >>Caution: These macros work only in black parts of the text. >> >>In blue parts you must substitute >> \mpiiidotiMergeNEWforSINGLEendI% >>by >> \mpiiidotiMergeNEWforSINGLEendII% >> >> >>The highlighting is done with red color. >>(There are only a few other sentences from me magenta. >> Therefore red should be the best to highlight the round-two modifications.) >> >>----------------------------------------------------- >>Using svn: >>Before you start to make changes: >> >> cd ....your_directory..../trunk/MPI-2.1/ >> svn update >> >>to get the newest sources. >> >>After you made changes, please call make and check mpi-report.pdf >>to guarantee that all your changes are really highlighted with *red* color. >> >>When you make the first svn commit after you received a new username with >>write-permission, you must use the aditional option >> >> --username your_new_user_name >> >>Please commit with >> >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' >> >>Please commit as soon as you finished the changes and after you have >>checked the red color. >> >>-------------------------------------------------- >> >>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) >> >> > > > >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 > > > From rabenseifner at [hidden] Fri Apr 18 03:31:58 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 18 Apr 2008 10:31:58 +0200 Subject: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: <4807F2DE.5020300@llnl.gov> Message-ID: Hi Adam, okay. Please send me a short reply when you have finished coll.tex. Thanks and best regards Rolf On Thu, 17 Apr 2008 18:01:18 -0700 Adam Moody wrote: > Hi Rolf, > I'll need Friday the 18th to incorporate Torsten's comments into the > Collectives chapter. I missed them when he first sent them. > -Adam > > Rolf Rabenseifner wrote: > > >All authors (except Rich [pt2pt and datatypes]), > > > >- The authors get back the write-token until Thursday, Apr. 17. > > (If you need also Friday Apr. 18, then please inform me!!) > >- All stuff that is not done until that point, will be defered to MPI-2.2! > > > >This is the last reminder and chance for latest updates **today**. > > > >(Details on the WORKPLAN, see mail below) > > > >Best regards > >Rolf > > > > > >On Sun, 13 Apr 2008 00:05:37 +0200 > > "Rolf Rabenseifner" wrote: > > > > > >>Dear chapter author, dear reviewer, > >> > >>This e-mail is the first preparation of the official reading. > >>Please read carefully. > >> > >>Again,we have a stable and consistent draft. > >>It is SVN revision 108 and pdf and ps are on > >> http://www.hlrs.de/mpi/mpi21/doc/ > >>(username and password are mpi21) > >> > >>Nearly all chapters have received an update by the chapters' authors. > >>Not finished is - as far as I can see > >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > >> - Datatypes [it was split from Point-to-point] (Rich Graham) > >>and full MPI-2 based chapters (maybe without need for updates) > >> - Terms (Tony Skjellum) > >> - External Interfaces (Bronis de Supinski) > >> - Profiling (Bronis de Supinski) > >>Therefore, review can start in all chapters, except the datatype chapter. > >> > >>IMPORTANT for authors: > >>If you make further modifications, please be sure that you use > >>the macros and that your modification (or at least an delete-anchor) > >>is printed **red**. (Details on using the macros, see below.) > >>Please check red color in the resulting mpi-report.pdf before you > >>svn commit your changes. > >>As far as I can see, all changes up to now may have no problem > >>for acceptance by the Forum. > >>At this late stage, I would recommend to do only changes that do > >>not need intensive debates at the Forum meeting. Such things > >>would be MPI-2.2 modifications. > >> > >>IMPORTANT for reviewers: > >>- 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). > >>- Please make all comments in the format > >> > >>---------------------------------------------------------------------------------- > >>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.) > >>---------------------------------------------------------------------------------- > >> > >>- Please send only review items that are in the category > >> -- ERROR, must be fixed. > >>- If you want to send an item in the categories > >> -- Nice to have, > >> -- Editorial proposal (like move xxx to yyy), > >> -- Clarification which needs Forum decisions, > >> -- ... > >> then please substitute the __ by 22, because then it should be > >> handled in MPI-2.2. > >> > >>This format is used in > >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > >>where all reviews are filed in. > >>(I'll substitute your xx by the next number. If you have more than > >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) > >> > >>Please use this format. I'll have only a few minutes between two flights > >>to put all reviews together. > >> > >>WORKPLAN: > >>- The authors get back the write-token until Thursday, Apr. 17. > >> (If you need also Friday Apr. 18, then please inform me!!) > >>- All stuff that is not done until that point, will be defered to MPI-2.2! > >>- I'm on travel and may not be able to respond on e-mails this week. > >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > >> final version for all final reviews and for the official reading. > >>- Version Apr. 17 together with all your review mails will be the > >> basis for the official reading. > >>- Reviews until Friday, Apr. 25. according the format above. > >>- Saturday, Apr. 26: > >> I will put all reviews together to have unique numbers. > >> > >>Best regards > >>Rolf > >> > >> > >>Annex: The rules for authors: > >> > >>The goals of your work as chapter author: > >>----------------------------------------- > >> > >>- Remove references to MPI-1 and MPI-2. > >>- Substitute by MPI. > >>- Necessary modifications to achieve this goal. > >> > >>With this, we should have a single MPI-2.1 standard that does > >>not "know" the MPI-1 or MPI-2 history of individual functions. > >> > >>** This should be mainly a task in the area of chapter-introductions. > >>** Please, never change the wording of function definitions. > >> > >>Exceptions: > >>- There are routines that are deprecated and that are > >> already referenced in a consistent way. > >> My recommendation: > >> Current wording: > >> There are *new* function, and existing are now deprecated. > >> Proposal: > >> There are functions, and there exist also deprecated functions > >> with (nearly) same functionality but deprecated due to some lack > >> in the bindings (or functionality) > >>- There is history information in the frontmatter. > >>- there is a change-log annex with limited memory (only previous version) > >> > >>Technical editing rule: > >>----------------------- > >> > >>You must identify all of your changes: > >> > >>a) new/modified wording - you are highlighting your new/modified wording with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > >>.... your modified / new wording .... > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > >> > >>b) Moved paragraphs, sentences, ... - you are highlighting the first word > >> of the moved text with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > >>First-word > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > >>... rest of the moved text.... > >>% MPI-2.1 round-two - end of text-move > >> > >>c) If you want to delete text (i.e. not only a move to another location), > >> the please us > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > >>Last word of the previous text > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > >> > >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > >>% the text you delete must be preceded with "% " > >>% deprecated text > >>% ... > >>% deprecated text > >>% MPI-2.1 round-two - end of deteted text > >> > >> Additionally, you must add this outcommented text to the end of > >> removed_source.tex > >> > >>Caution: These macros work only in black parts of the text. > >> > >>In blue parts you must substitute > >> \mpiiidotiMergeNEWforSINGLEendI% > >>by > >> \mpiiidotiMergeNEWforSINGLEendII% > >> > >> > >>The highlighting is done with red color. > >>(There are only a few other sentences from me magenta. > >> Therefore red should be the best to highlight the round-two modifications.) > >> > >>----------------------------------------------------- > >>Using svn: > >>Before you start to make changes: > >> > >> cd ....your_directory..../trunk/MPI-2.1/ > >> svn update > >> > >>to get the newest sources. > >> > >>After you made changes, please call make and check mpi-report.pdf > >>to guarantee that all your changes are really highlighted with *red* color. > >> > >>When you make the first svn commit after you received a new username with > >>write-permission, you must use the aditional option > >> > >> --username your_new_user_name > >> > >>Please commit with > >> > >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > >> > >>Please commit as soon as you finished the changes and after you have > >>checked the red color. > >> > >>-------------------------------------------------- > >> > >>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) > >> > >> > > > > > > > >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 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) From rabenseifner at [hidden] Fri Apr 18 03:35:26 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Fri, 18 Apr 2008 10:35:26 +0200 Subject: [Mpi-21] 2nd reply - Re: AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008 In-Reply-To: <4807F2DE.5020300@llnl.gov> Message-ID: Please send me a revised mail from Torstens mail where you mark all done items with DON2 and all other with the defined mark-ups as shown on http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt Thanks Rolf On Thu, 17 Apr 2008 18:01:18 -0700 Adam Moody wrote: > Hi Rolf, > I'll need Friday the 18th to incorporate Torsten's comments into the > Collectives chapter. I missed them when he first sent them. > -Adam > > Rolf Rabenseifner wrote: > > >All authors (except Rich [pt2pt and datatypes]), > > > >- The authors get back the write-token until Thursday, Apr. 17. > > (If you need also Friday Apr. 18, then please inform me!!) > >- All stuff that is not done until that point, will be defered to MPI-2.2! > > > >This is the last reminder and chance for latest updates **today**. > > > >(Details on the WORKPLAN, see mail below) > > > >Best regards > >Rolf > > > > > >On Sun, 13 Apr 2008 00:05:37 +0200 > > "Rolf Rabenseifner" wrote: > > > > > >>Dear chapter author, dear reviewer, > >> > >>This e-mail is the first preparation of the official reading. > >>Please read carefully. > >> > >>Again,we have a stable and consistent draft. > >>It is SVN revision 108 and pdf and ps are on > >> http://www.hlrs.de/mpi/mpi21/doc/ > >>(username and password are mpi21) > >> > >>Nearly all chapters have received an update by the chapters' authors. > >>Not finished is - as far as I can see > >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > >> - Datatypes [it was split from Point-to-point] (Rich Graham) > >>and full MPI-2 based chapters (maybe without need for updates) > >> - Terms (Tony Skjellum) > >> - External Interfaces (Bronis de Supinski) > >> - Profiling (Bronis de Supinski) > >>Therefore, review can start in all chapters, except the datatype chapter. > >> > >>IMPORTANT for authors: > >>If you make further modifications, please be sure that you use > >>the macros and that your modification (or at least an delete-anchor) > >>is printed **red**. (Details on using the macros, see below.) > >>Please check red color in the resulting mpi-report.pdf before you > >>svn commit your changes. > >>As far as I can see, all changes up to now may have no problem > >>for acceptance by the Forum. > >>At this late stage, I would recommend to do only changes that do > >>not need intensive debates at the Forum meeting. Such things > >>would be MPI-2.2 modifications. > >> > >>IMPORTANT for reviewers: > >>- 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). > >>- Please make all comments in the format > >> > >>---------------------------------------------------------------------------------- > >>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.) > >>---------------------------------------------------------------------------------- > >> > >>- Please send only review items that are in the category > >> -- ERROR, must be fixed. > >>- If you want to send an item in the categories > >> -- Nice to have, > >> -- Editorial proposal (like move xxx to yyy), > >> -- Clarification which needs Forum decisions, > >> -- ... > >> then please substitute the __ by 22, because then it should be > >> handled in MPI-2.2. > >> > >>This format is used in > >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > >>where all reviews are filed in. > >>(I'll substitute your xx by the next number. If you have more than > >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) > >> > >>Please use this format. I'll have only a few minutes between two flights > >>to put all reviews together. > >> > >>WORKPLAN: > >>- The authors get back the write-token until Thursday, Apr. 17. > >> (If you need also Friday Apr. 18, then please inform me!!) > >>- All stuff that is not done until that point, will be defered to MPI-2.2! > >>- I'm on travel and may not be able to respond on e-mails this week. > >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > >> final version for all final reviews and for the official reading. > >>- Version Apr. 17 together with all your review mails will be the > >> basis for the official reading. > >>- Reviews until Friday, Apr. 25. according the format above. > >>- Saturday, Apr. 26: > >> I will put all reviews together to have unique numbers. > >> > >>Best regards > >>Rolf > >> > >> > >>Annex: The rules for authors: > >> > >>The goals of your work as chapter author: > >>----------------------------------------- > >> > >>- Remove references to MPI-1 and MPI-2. > >>- Substitute by MPI. > >>- Necessary modifications to achieve this goal. > >> > >>With this, we should have a single MPI-2.1 standard that does > >>not "know" the MPI-1 or MPI-2 history of individual functions. > >> > >>** This should be mainly a task in the area of chapter-introductions. > >>** Please, never change the wording of function definitions. > >> > >>Exceptions: > >>- There are routines that are deprecated and that are > >> already referenced in a consistent way. > >> My recommendation: > >> Current wording: > >> There are *new* function, and existing are now deprecated. > >> Proposal: > >> There are functions, and there exist also deprecated functions > >> with (nearly) same functionality but deprecated due to some lack > >> in the bindings (or functionality) > >>- There is history information in the frontmatter. > >>- there is a change-log annex with limited memory (only previous version) > >> > >>Technical editing rule: > >>----------------------- > >> > >>You must identify all of your changes: > >> > >>a) new/modified wording - you are highlighting your new/modified wording with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > >>.... your modified / new wording .... > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > >> > >>b) Moved paragraphs, sentences, ... - you are highlighting the first word > >> of the moved text with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > >>First-word > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > >>... rest of the moved text.... > >>% MPI-2.1 round-two - end of text-move > >> > >>c) If you want to delete text (i.e. not only a move to another location), > >> the please us > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > >>Last word of the previous text > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > >> > >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > >>% the text you delete must be preceded with "% " > >>% deprecated text > >>% ... > >>% deprecated text > >>% MPI-2.1 round-two - end of deteted text > >> > >> Additionally, you must add this outcommented text to the end of > >> removed_source.tex > >> > >>Caution: These macros work only in black parts of the text. > >> > >>In blue parts you must substitute > >> \mpiiidotiMergeNEWforSINGLEendI% > >>by > >> \mpiiidotiMergeNEWforSINGLEendII% > >> > >> > >>The highlighting is done with red color. > >>(There are only a few other sentences from me magenta. > >> Therefore red should be the best to highlight the round-two modifications.) > >> > >>----------------------------------------------------- > >>Using svn: > >>Before you start to make changes: > >> > >> cd ....your_directory..../trunk/MPI-2.1/ > >> svn update > >> > >>to get the newest sources. > >> > >>After you made changes, please call make and check mpi-report.pdf > >>to guarantee that all your changes are really highlighted with *red* color. > >> > >>When you make the first svn commit after you received a new username with > >>write-permission, you must use the aditional option > >> > >> --username your_new_user_name > >> > >>Please commit with > >> > >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > >> > >>Please commit as soon as you finished the changes and after you have > >>checked the red color. > >> > >>-------------------------------------------------- > >> > >>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) > >> > >> > > > > > > > >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 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) From moody20 at [hidden] Fri Apr 18 14:41:49 2008 From: moody20 at [hidden] (Adam Moody) Date: Fri, 18 Apr 2008 12:41:49 -0700 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: <20080413183551.GS9521@benten.cs.indiana.edu> Message-ID: <4808F97D.7080000@llnl.gov> 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-report.pdf -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 > > > * -------------- next part -------------- An HTML attachment was scrubbed... URL: From rabenseifner at [hidden] Sat Apr 19 07:37:49 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sat, 19 Apr 2008 14:37:49 +0200 Subject: [Mpi-21] AUTHORS - write token is back at me (except pt2pt + datatypes) Message-ID: 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) From htor at [hidden] Sat Apr 19 12:07:12 2008 From: htor at [hidden] (Torsten Hoefler) Date: Sat, 19 Apr 2008 13:07:12 -0400 Subject: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008 In-Reply-To: <4808F97D.7080000@llnl.gov> Message-ID: <20080419170712.GQ21234@benten.cs.indiana.edu> 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-report.pdf > -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 From rabenseifner at [hidden] Sat Apr 19 16:06:06 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sat, 19 Apr 2008 23:06:06 +0200 Subject: [Mpi-21] All REVIEWERS - Final 1.3 and 2.1 review Message-ID: 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.pdf 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) From rabenseifner at [hidden] Mon Apr 21 13:38:37 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Mon, 21 Apr 2008 20:38:37 +0200 Subject: [Mpi-21] Formal MPI-2.1 Review Message-ID: 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) From kannan.narasimhan at [hidden] Sat Apr 26 12:13:12 2008 From: kannan.narasimhan at [hidden] (Narasimhan, Kannan) Date: Sat, 26 Apr 2008 17:13:12 +0000 Subject: [Mpi-21] Formal MPI-2.1 Review In-Reply-To: Message-ID: 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 From bosilca at [hidden] Sat Apr 26 13:09:35 2008 From: bosilca at [hidden] (George Bosilca) Date: Sat, 26 Apr 2008 14:09:35 -0400 Subject: [Mpi-21] Formal MPI-2.1 Review In-Reply-To: Message-ID: <898BC4FA-4F4C-4D14-9E28-5E226A301960@eecs.utk.edu> 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 * -------------- next part -------------- A non-text attachment was scrubbed... Name: inquiry.diff Type: application/octet-stream Size: 3330 bytes Desc: inquiry.diff URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2423 bytes Desc: smime.p7s URL: From rabenseifner at [hidden] Sun Apr 27 13:09:37 2008 From: rabenseifner at [hidden] (Rolf Rabenseifner) Date: Sun, 27 Apr 2008 20:09:37 +0200 Subject: [Mpi-21] Meeting Apr. 28-30 - MPI-1.3 and MPI-2.1 Message-ID: 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) From jsquyres at [hidden] Mon Apr 28 12:32:37 2008 From: jsquyres at [hidden] (Jeff Squyres) Date: Mon, 28 Apr 2008 12:32:37 -0500 Subject: [Mpi-21] problems with 19 Apr document Message-ID: <1CE89319-D9EF-480E-A8A4-80341E16E724@cisco.com> 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 From keller at [hidden] Mon Apr 28 20:27:55 2008 From: keller at [hidden] (Rainer Keller) Date: Tue, 29 Apr 2008 03:27:55 +0200 Subject: [Mpi-21] Formal MPI-2.1 Review In-Reply-To: Message-ID: <200804290327.55568.keller@hlrs.de> 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 * -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: changes_to_mpi-2.1_chapter12.txt URL: From keller at [hidden] Tue Apr 29 09:27:26 2008 From: keller at [hidden] (Rainer Keller) Date: Tue, 29 Apr 2008 16:27:26 +0200 Subject: [Mpi-21] MPI-2.1: Review of Chapter 1 and buglets in Chapter 15 Message-ID: <200804291627.26830.keller@hlrs.de> Dear Rolf, please find enclosed the changes to Chapter 1 in the file below. Also, please note, that in Chapter 15, starting with p441, l38 the word language is misspelled several times: p441, l38 -- laguage --> language. With best regards, Rainer -- ---------------------------------------------------------------- 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 * -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: changes_to_mpi-2.1_chapter1.txt URL: From traff at [hidden] Tue Apr 29 09:32:26 2008 From: traff at [hidden] (Jesper Traff) Date: Tue, 29 Apr 2008 16:32:26 +0200 Subject: [Mpi-21] Chapter 1 && 2 minor comments In-Reply-To: <1CE89319-D9EF-480E-A8A4-80341E16E724@cisco.com> Message-ID: <039401c8aa05$da36ec10$e081270a@ccrlnece.de> Dear all, here are some minor typos and sugestiosn for chaps 1&2 Jesper --- General: "message-passing" or "message passing"? Chapter 1: p.4, line 3: electonically -> electronically p.4, line 38: "hybrid architectures," - add space p.5 (ff): Update "Miscellany chapter" to something with info object p.6, line 17: drop "more convenient methods of constructing intercommunicators" (not in that chapter) p.6, line 22: correct chapter name (add "Caching") Chapter 2: p.94).", line 14: MPI-2 -> MPI p.9, line 15-19: drop (or reformulate) p.9, line 40-45: reformulate: "In many cases MPI names for C functions are of the form Class_action_subset. This convention originated with MPI-1. Since MPI-2 an attempt has been made to standardize the names of MPI functions according to the following rules. The C++ bindings in particular follow these rules (see Sectoion 2.6)." p.10, line 15: MPI-1 functions -> some MPI functions (that were defined during the MPI-1 process) p.10, line 26-30: bullet unintelligible. Change: An argument whose value may be used by a call but may not be updated is marked as IN An argument that may be updated by a call but whose value will not be used is marked as OUT An argument whose value may be used and that may be updated is marked as INOUT p.10, line 47: too much blank LaTeX space p.11, line 38: add: ".it is freed." -> ".it is freed, and becomes inactive if it was persistent." p.16, line 11: since MPI-2. -> since better solutions were provided with MPI-2. p.16, line 14: replace with: "With MPI-2, these functions were given new names with new bindings for the address arguments." p.16, line 19: "error-prone, ." -> "error-prone. The MPI-2 ." p.16, line 28: Change to "Originally MPI-1.1 provided bindings for Fortran 77. These bindings are retained, but they are now." p.16, line 45: Give some reason or excuse: "Unfortunately but unavoidably, the MPI Fortran bindings." p.18, line 6: MPI-2 -> MPI p.18, line 10: can't -> cannot p.19, line 45: MPI-2 -> MPI p.19, line 46: "the new MPI-2." -> "an MPI function is related to a function defined already for MPI-1 p.19, line 48: MPI-2 -> MPI p.20, line 2: drop "for MPI-1" p.20, line 3: "MPI-1 name is" -> "MPI name may be" p.23, line 3: drop latter part of sentence, "are described in Chapter ". p.23, line 32: MPI-2 -> MPI From traff at [hidden] Tue Apr 29 10:47:23 2008 From: traff at [hidden] (Jesper Traff) Date: Tue, 29 Apr 2008 17:47:23 +0200 Subject: [Mpi-21] Chapter 5 comments/suggestions In-Reply-To: Message-ID: <03ff01c8aa10$587c02e0$e081270a@ccrlnece.de> hi all uggestions/changes for Chapter 5 jesper (and adam) * -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Chap5_Jespers_comments.txt URL: From traff at [hidden] Tue Apr 29 11:51:24 2008 From: traff at [hidden] (Jesper Traff) Date: Tue, 29 Apr 2008 18:51:24 +0200 Subject: [Mpi-21] Chapter 3-4 minor comments and suggestions In-Reply-To: <03ff01c8aa10$587c02e0$e081270a@ccrlnece.de> Message-ID: <044001c8aa19$46718c10$e081270a@ccrlnece.de> dear all, ome final, minor comments to chapters 3 and 4 jesper * -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Chap3-Chap4.txt URL: