Mpi-21
Threads by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
April 2008
- 1 participants
- 103 discussions
On Wed, 02 Apr 2008 18:25:45 +0200
"Rolf Rabenseifner" <rabenseifner_at_[hidden]> 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
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.
> >
> >
1
0
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.
>
>
1
0
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.
1
0
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
1
0
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)
> >
1
0
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)
>
*
1
0
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] Comments on merged MPI-2.1 document (as per March meeting)
by unknown＠example.com 02 Apr '08
by unknown＠example.com 02 Apr '08
02 Apr '08
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 <traff_at_it.neclab.eu> 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)
1
0
02 Apr '08
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?
1
0