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

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 07 Apr '08

07 Apr '08

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 <jsquyres_at_[hidden]> 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 <jsquyres_at_[hidden]> 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

1 0

2.1 cleanup or MPI 2.2?
by unknown＠example.com 07 Apr '08

07 Apr '08

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 *

1 0

AUTHORS of MPI-2.1 - SVN rules
by unknown＠example.com 04 Apr '08

04 Apr '08

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)

1 0

AUTHORS of MPI-2.1 - New directory structure
by unknown＠example.com 04 Apr '08

04 Apr '08

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)

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 04 Apr '08

04 Apr '08

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) *

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 04 Apr '08

04 Apr '08

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" <alexander.supalov_at_[hidden]> 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.

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 04 Apr '08

04 Apr '08

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" <alexander.supalov_at_[hidden]> 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)

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 04 Apr '08

04 Apr '08

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" <bronis_at_[hidden]> 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)

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - Workplan
by unknown＠example.com 04 Apr '08

04 Apr '08

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 <jsquyres_at_[hidden]> 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 <jsquyres_at_[hidden]> 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)

1 0

Re: [Mpi-21] TODO - AUTHORS of MPI-2.1 - delete text
by unknown＠example.com 04 Apr '08

04 Apr '08

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" <rabenseifner_at_[hidden]> 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" <bronis_at_[hidden]> 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)

1 0