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

Re: [mpi-21] Ballot 4 proposal: "static" predefined MPI C++ handles
by unknown＠example.com 18 Jan '08

18 Jan '08

Aren't we also removing the const :) The text would still be incorrect; in some implementations the MPI::COMM_WORLD is not const qualified. I suggest removing this sentence. (In C++....) -----Original Message----- From: owner-mpi-21_at_[hidden] [mailto:owner-mpi-21_at_[hidden]] On Behalf Of Jeff Squyres Sent: Friday, January 18, 2008 10:29 AM To: mpi-21_at_[hidden]; mpi-21_at_[hidden] Subject: [mpi-21] Ballot 4 proposal: "static" predefined MPI C++ handles This mail is a proposal for MPI 2.1, ballot 4. NOTE: This mail is a slight re-formatting of http://www.mpi-forum.org/mail_archive/mpi-21/2008/01/msg00119.html to be in ballot proposal format. In MPI 2.0, page 9, lines 17-18 state: "MPI provides certain predefined opaque objects and predefined, static handles to these objects. The user must not free such objects. In C+ +, this is enforced by declaring the handles to these predefined objects to be {\tt static const}." The "static" in the last sentence should be deleted. Rationale: When using namespaces, all the MPI symbols are in the namespace and objects do not need to be static in a singleton object for the MPI class. Specifically: they are static *only* if you are using the singleton object for the MPI class. The context for the statement is talking about the constant quality; the "static" is superfluous -- describing whether "static" is necessary or not would be too much for this section. -- Jeff Squyres Cisco Systems

1 0

Withdraw errata request
by unknown＠example.com 18 Jan '08

18 Jan '08

Per http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/ , I withdraw my initial query about "MPI_FINALIZE in MPI-2 (with spawn)" (mail discussing: http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/discus…) . There is no problem; there is no need for clarification. Let's remove it from the list of outstanding issues. -- Jeff Squyres Cisco Systems

1 0

Ballot 4 proposal: "static" predefined MPI C++ handles
by unknown＠example.com 18 Jan '08

18 Jan '08

This mail is a proposal for MPI 2.1, ballot 4. NOTE: This mail is a slight re-formatting of http://www.mpi-forum.org/mail_archive/mpi-21/2008/01/msg00119.html to be in ballot proposal format. In MPI 2.0, page 9, lines 17-18 state: "MPI provides certain predefined opaque objects and predefined, static handles to these objects. The user must not free such objects. In C+ +, this is enforced by declaring the handles to these predefined objects to be {\tt static const}." The "static" in the last sentence should be deleted. Rationale: When using namespaces, all the MPI symbols are in the namespace and objects do not need to be static in a singleton object for the MPI class. Specifically: they are static *only* if you are using the singleton object for the MPI class. The context for the statement is talking about the constant quality; the "static" is superfluous -- describing whether "static" is necessary or not would be too much for this section. -- Jeff Squyres Cisco Systems

1 0

Re: [mpi-21] MPI 2.1 Abstract text
by unknown＠example.com 18 Jan '08

18 Jan '08

Erez, I used at the beginning MPI 1.1 and MPI-2 documents to reference the major documents that have been produced by MPI-1 and MPI-2 Forum. And I'm summarizing all other input in "and errata documents from the MPI Forum" (which are small compared to the work of MPI 1.1 and MPI-2). At the beginning, I'm intentionally not separate 1.2 and 2.0. I'm referencing the documents (i.e. "MPI 1.1 and MPI-2" and not "MPI 1.1 + 1.2 + 2.0") In the further parts of the abstract, I point to MPI 1.2 and MPI 1.3. Best regards Rolf On Fri, 18 Jan 2008 09:12:52 -0800 Erez Haba <erezh_at_[hidden]> wrote: >Shouldn't the first paragraph use the 1.3 version? (rather than 1.1 or 1.2) E.g., > >This document describes the MPI standard version 2.1 in one >combined document. This document combines the content from the >previous standards "MPI: A Message-Passing Interface Standard, ><date>" (MPI-1.3) and "MPI-2: Extensions to the >Message-Passing Interface, July, 1997" (MPI-1.3 and MPI-2.0) >and errata documents from the MPI Forum. > > >-----Original Message----- >From: owner-mpi-21_at_[hidden] [mailto:owner-mpi-21_at_[hidden]] On Behalf Of Bronis R. de Supinski >Sent: Friday, January 18, 2008 7:52 AM >To: Mailing list for discussion of MPI 2.1 >Cc: mpi-21_at_[hidden] >Subject: Re: [mpi-21] MPI 2.1 Abstract text > > >Rolf: > >Re: >> This is the currently proposed Abstract for MPI 2.1: > >A couple minor editing suggestions: > >---------------------------------------------------------------------- >This document describes the MPI standard version 2.1 in one >combined document. This document combines the content from the >previous standards "MPI: A Message-Passing Interface Standard, >June 12, 1995" (MPI-1.1) and "MPI-2: Extensions to the >Message-Passing Interface, July, 1997" (MPI-1.2 and MPI-2.0) >and errata documents from the MPI Forum. >The standard MPI-1.1 includes point-to-point message passing, >collective communications, group and communicator concepts, >process topologies, environmental management, and a profiling >interface. Language bindings for C and Fortran are defined. >The MPI-1.2 chapter of the MPI-2 document contains clarifications >and corrections to the MPI-1.1 standard and defines MPI-1.2. >Together with corrections, these MPI-1 documents were combined >to MPI 1.3 (<data>, 2008) which was used as input for this document. >The second input is the MPI-2 part of the MPI-2 document, which >describes additions to the MPI-1 standard and defines the >MPI standard version 2.0. These include miscellaneous topics, >process creation and management, one-sided communications, >extended collective operations, external interfaces, I/O, >and additional language bindings (C++). Additional clarifications >and errata corrections to MPI-2.0 are also included. >---------------------------------------------------------------------- > >I changed "book" to "document" for consistency, and added a >"The " and a comma needed for grammatical correctness. > >Bronis > >> It is based on the abstract of MPI 2.0. >> MPI 1.1 hadn't any abstract. >> >> This abstact should tell the main features of MPI. >> It should not give a full history. This is done by the versions page. >> Hints from the MPI Forum meeting Jan. 2008 are also included, >> i.e., the major sources are referenced, but also the steps >> between, i.e., the clarifications and MPI 1.3. >> >> -------------------------------------------------------- >> Discussion should be done through the new mailing list >> mpi-21_at_cs.uiuc.edu. >> >> I have sent out this mail with CC through the old general list >> mpi-21_at_[hidden] >> >> Best regards >> Rolf >> >> >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >> _______________________________________________ >> mpi-21 mailing list >> mpi-21_at_[hidden] >> http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21 >> >> > > >_______________________________________________ >mpi-21 mailing list >mpi-21_at_[hidden] >http://lists.cs.uiuc.edu/mailman/listinfo/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] problem with MPI_Get_count and MPI_Probe
by unknown＠example.com 18 Jan '08

18 Jan '08

This is a proposal for MPI 2.1, Ballot 4. This is a follow up to: Datatypes and MPI_PROBE in http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/index.… with mail discussion in http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/discus… Proposal for MPI 2.1, Ballot 4: ------------------------------- MPI 1.1, page 222, line 48 reads used after a call to MPI_PROBE. (End of rationale.) but should read used after a call to MPI_PROBE or MPI_IPROBE. With a status returned from MPI_PROBE or MPI_IPROBE, the same dataypes are allowed as in a call to MPI_RECV to receive this message. (End of rationale.) Advice to users. To allocate the appropriate amount of memory as receive buffer, the same datatype as in the following receive call should be used to determine the needed space. In portable programs due to possible data conversions, it is not guaranteed that the count returned by MPI_GET_COUNT with datatype MPI_BYTE is the correct amount of needed memory space in the receive buffer (although MPI_BYTE is matching every datatype). (End of advice to users.) ------------------------------- Reason for the first part: The current MPI-1.1 text says "The datatype argument should match the argument provided by the receive call that set the status variable." With MPI_PROBE, there isn't such a receive call. Reason for the advice to users: It helps to write portable code. Because malloc needs a byte count, users may write wrong programs by using MPI_BYTE. ------------------------------- Discussion should be done through the new mailing list mpi-21_at_cs.uiuc.edu. I have sent out this mail with CC through the old general list mpi-21_at_[hidden] 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] MPI 2.1 Abstract text
by unknown＠example.com 18 Jan '08

18 Jan '08

Shouldn't the first paragraph use the 1.3 version? (rather than 1.1 or 1.2) E.g., This document describes the MPI standard version 2.1 in one combined document. This document combines the content from the previous standards "MPI: A Message-Passing Interface Standard, <date>" (MPI-1.3) and "MPI-2: Extensions to the Message-Passing Interface, July, 1997" (MPI-1.3 and MPI-2.0) and errata documents from the MPI Forum. -----Original Message----- From: owner-mpi-21_at_[hidden] [mailto:owner-mpi-21_at_[hidden]] On Behalf Of Bronis R. de Supinski Sent: Friday, January 18, 2008 7:52 AM To: Mailing list for discussion of MPI 2.1 Cc: mpi-21_at_[hidden] Subject: Re: [mpi-21] MPI 2.1 Abstract text Rolf: Re: > This is the currently proposed Abstract for MPI 2.1: A couple minor editing suggestions: ---------------------------------------------------------------------- This document describes the MPI standard version 2.1 in one combined document. This document combines the content from the previous standards "MPI: A Message-Passing Interface Standard, June 12, 1995" (MPI-1.1) and "MPI-2: Extensions to the Message-Passing Interface, July, 1997" (MPI-1.2 and MPI-2.0) and errata documents from the MPI Forum. The standard MPI-1.1 includes point-to-point message passing, collective communications, group and communicator concepts, process topologies, environmental management, and a profiling interface. Language bindings for C and Fortran are defined. The MPI-1.2 chapter of the MPI-2 document contains clarifications and corrections to the MPI-1.1 standard and defines MPI-1.2. Together with corrections, these MPI-1 documents were combined to MPI 1.3 (<data>, 2008) which was used as input for this document. The second input is the MPI-2 part of the MPI-2 document, which describes additions to the MPI-1 standard and defines the MPI standard version 2.0. These include miscellaneous topics, process creation and management, one-sided communications, extended collective operations, external interfaces, I/O, and additional language bindings (C++). Additional clarifications and errata corrections to MPI-2.0 are also included. ---------------------------------------------------------------------- I changed "book" to "document" for consistency, and added a "The " and a comma needed for grammatical correctness. Bronis > It is based on the abstract of MPI 2.0. > MPI 1.1 hadn't any abstract. > > This abstact should tell the main features of MPI. > It should not give a full history. This is done by the versions page. > Hints from the MPI Forum meeting Jan. 2008 are also included, > i.e., the major sources are referenced, but also the steps > between, i.e., the clarifications and MPI 1.3. > > -------------------------------------------------------- > Discussion should be done through the new mailing list > mpi-21_at_cs.uiuc.edu. > > I have sent out this mail with CC through the old general list > mpi-21_at_[hidden] > > Best regards > Rolf > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21 > >

1 0

Re: [mpi-21] MPI-2 MPI_Comm_spawn inconsistency
by unknown＠example.com 18 Jan '08

18 Jan '08

This is a proposal for MPI 2.1, Ballot 4. This is a follow up to: Significance of non-root arguments to MPI_COMM_SPAWN in http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/index.… with mail discussion in http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/discus… The problem may be clarified with the following proposal Proposal for MPI 2.1, Ballot 4: ------------------------------- Add in MPI-2.0, page 88, after line 24: Advice to users. If the non-root processes do not use MPI_ERRCODES_IGNORE, then they have to allocate the appropriate number of entries (see maxproc at root) in the array_of_errcodes although the maxproc argument is unused in non-root processes. (End of advice to users.) ------------------------------- Discussion should be done through the new mailing list mpi-21_at_cs.uiuc.edu. I have sent out this mail with CC through the old general list mpi-21_at_[hidden] 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] MPI 2.1 Versions history
by unknown＠example.com 18 Jan '08

18 Jan '08

This looks good enough to me. Note that the <date> for Version 2.0 is July 18 (as cited in the 2.1 bullet). On Jan 18, 2008, at 10:38 AM, Rolf Rabenseifner wrote: > This is the currently proposed Versions History as shown on the > back-page of the title page > > ---------------------------------------------------------------------- > Version 2.1: <date>, 2008. This document combines the previous > documents MPI 1.3 (????, 2008) and MPI-2.0 (July 18, 1997). > Certain parts of MPI 2.0, such as some sections of Chapter 4, > Miscellany, and Chapter 7, Extended Collective Operations have > been merged into the Chapters of MPI 1.3. Additional errata and > clarifications collected by the MPI Forum are also included in > this document. > > Version 1.3: <date>, 2008. This document combines the previous > documents MPI 1.1 (June 12, 1995) and the MPI 1.2 Chapter in MPI-2 > (July 18, 1997). Additional errata collected by the MPI Forum > referring to MPI 1.1 and MPI 1.2 are also included in this > document. > > Version 2.0: <date>, 1997. Beginning after the release of > MPI 1.1, the MPI Forum began meeting to consider corrections and > extensions. MPI-2 has been focused on process creation and > management, one-sided communications, extended collective > communications, external interfaces and parallel I/O. A miscellany > chapter discusses items that don't fit elsewhere, in particular > language interoperability. > > Version 1.2: July 18, 1997. The MPI-2 Forum introduced MPI 1.2 ... > > Version 1.1: June, 1995. Beginning in March, 1995, the Message ... > > Version 1.0: June, 1994. The Message Passing Interface Forum ... > ---------------------------------------------------------------------- > > It is based on the existing text from MPI 1.1 > (For completness, I repeated the already voted text about MPI 1.3) > The words "Version x.x: date, year" will be printed bold face > (as shown in MPI 1.1 on the second frontmatter page). > > Are there proposals for modifications? > > > Discussion should be done through the new mailing list > mpi-21_at_cs.uiuc.edu. > > I have sent out this mail with CC through the old general list > mpi-21_at_[hidden] > > 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

Incorrect use of MPI_IN_PLACE in description of MPI_ALLGATHER and MPI_ALLGATHERV
by unknown＠example.com 18 Jan '08

18 Jan '08

This is a proposal for MPI 2.1, Ballot 4. This is a follow up to: Incorrect use of MPI_IN_PLACE in description of MPI_ALLGATHER and MPI_ALLGATHERV http://www.cs.uiuc.edu/homes/wgropp/projects/parallel/MPI/mpi-errata/discus… Jeff is right with his error report. I propose to remove the wrong text, because this (wrong) analogy is not needed for understanding the meaning of "in place" in MPI_ALLGATHER and MPI_ALLGATHERV. Proposal for MPI 2.1, Ballot 4: ------------------------------- On MPI-2.0, page 159, lines 23-28, remove the text "Specifically, ... ... n-1." On MPI-2.0, page 158, lines 25-31, remove the text "Specifically, ... ... n-1." ------------------------------- Discussion should be done through the new mailing list mpi-21_at_cs.uiuc.edu. I have sent out this mail with CC through the old general list mpi-21_at_[hidden] 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] MPI 2.1 Abstract text
by unknown＠example.com 18 Jan '08

18 Jan '08

Rolf: Re: > This is the currently proposed Abstract for MPI 2.1: A couple minor editing suggestions: ---------------------------------------------------------------------- This document describes the MPI standard version 2.1 in one combined document. This document combines the content from the previous standards MPI: A Message-Passing Interface Standard, June 12, 1995 (MPI-1.1) and MPI-2: Extensions to the Message-Passing Interface, July, 1997 (MPI-1.2 and MPI-2.0) and errata documents from the MPI Forum. The standard MPI-1.1 includes point-to-point message passing, collective communications, group and communicator concepts, process topologies, environmental management, and a profiling interface. Language bindings for C and Fortran are defined. The MPI-1.2 chapter of the MPI-2 document contains clarifications and corrections to the MPI-1.1 standard and defines MPI-1.2. Together with corrections, these MPI-1 documents were combined to MPI 1.3 (<data>, 2008) which was used as input for this document. The second input is the MPI-2 part of the MPI-2 document, which describes additions to the MPI-1 standard and defines the MPI standard version 2.0. These include miscellaneous topics, process creation and management, one-sided communications, extended collective operations, external interfaces, I/O, and additional language bindings (C++). Additional clarifications and errata corrections to MPI-2.0 are also included. ---------------------------------------------------------------------- I changed "book" to "document" for consistency, and added a "The " and a comma needed for grammatical correctness. Bronis > It is based on the abstract of MPI 2.0. > MPI 1.1 hadn't any abstract. > > This abstact should tell the main features of MPI. > It should not give a full history. This is done by the versions page. > Hints from the MPI Forum meeting Jan. 2008 are also included, > i.e., the major sources are referenced, but also the steps > between, i.e., the clarifications and MPI 1.3. > > -------------------------------------------------------- > Discussion should be done through the new mailing list > mpi-21_at_cs.uiuc.edu. > > I have sent out this mail with CC through the old general list > mpi-21_at_[hidden] > > Best regards > Rolf > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.cs.uiuc.edu/mailman/listinfo/mpi-21 > >

1 0