- mpi-comments - mailman3.cels.anl.gov

Re: [Mpi-comments] typo in MPI_*_SET_ATTR parameter
by William Gropp 27 Apr '16

27 Apr '16

The definitions of IN and INOUT are given in section 2.3, page 10, and are not identical to the Fortran terms. INOUT means that the call may update the arguments - see lines 23-27 on page 10. The MPI standard is correct as is. Bill William Gropp Director, Parallel Computing Institute Thomas M. Siebel Chair in Computer Science Chief Scientist, NCSA University of Illinois Urbana-Champaign On Apr 27, 2016, at 6:37 PM, Gilles Gouaillardet <gilles(a)rist.or.jp> wrote: > Folks, > > i noticed 3 similar and minor typos in the MPI 3.1 standard > > > 1) MPI_COMM_SET_ATTR page 270 line 43 reads > > "INOUT comm ..." > > but should be > > "IN comm ..." > > > 2) MPI_WIN_SET_ATTR page 274 line 33 reads > > "INOUT win ..." > > but should be > > "IN win ..." > > > 3) MPI_TYPE_SET_ATTR page 278 line 3 reads > > "INOUT datatype ..." > > but should be > > "IN datatype ..." > > > note Fortran 2008 correctly reads "INTENT(IN)" > > > Cheers, > > > Gilles > _______________________________________________ > mpi-comments mailing list > mpi-comments(a)mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments

1 0

typo in MPI_*_SET_ATTR parameter
by Gilles Gouaillardet 27 Apr '16

27 Apr '16

Folks, i noticed 3 similar and minor typos in the MPI 3.1 standard 1) MPI_COMM_SET_ATTR page 270 line 43 reads "INOUT comm ..." but should be "IN comm ..." 2) MPI_WIN_SET_ATTR page 274 line 33 reads "INOUT win ..." but should be "IN win ..." 3) MPI_TYPE_SET_ATTR page 278 line 3 reads "INOUT datatype ..." but should be "IN datatype ..." note Fortran 2008 correctly reads "INTENT(IN)" Cheers, Gilles

1 0

Re: [Mpi-comments] Who is the owner of the 'MPI' acronym?
by Dorau, Lukasz 24 Feb '16

24 Feb '16

> -----Original Message----- > From: mpi-comments [mailto:[email protected]] On > Behalf Of Jeff Squyres (jsquyres) > Sent: Wednesday, February 24, 2016 5:03 AM > To: Comments on the MPI Standard <mpi-comments(a)lists.mpi-forum.org> > Subject: Re: [Mpi-comments] Who is the owner of the 'MPI' acronym? > > Are you asking if there is a trademark or other intellectual property restriction > on using the acronym "MPI"? > Exactly. > If so, you should probably consult a lawyer about > that. > > If you're asking if you can release an open source software project that contains > the name "MPI", if this software has nothing to do with the Message Passing > Interface as described by www.mpi-forum.org, it would be nice if you didn't. > Our project is a sort of persistent implementation of Message Passing Interface, so it has a lot to do with the Message Passing Interface. Lukasz > > On Feb 23, 2016, at 10:24 AM, Dorau, Lukasz <lukasz.dorau(a)intel.com> wrote: > > > > Hi, > > > > Can you tell me who is the owner of the 'MPI' acronym? > > > > I want to use this acronym in the name of the project that I am going to release > as open source project and I would like to ask the owner if I can use it... > > > > Regards, > > Lukasz > > > > > > _______________________________________________ > > mpi-comments mailing list > > mpi-comments(a)lists.mpi-forum.org > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments > > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpi-comments mailing list > mpi-comments(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments

1 0

Re: [Mpi-comments] Who is the owner of the 'MPI' acronym?
by Jeff Squyres (jsquyres) 23 Feb '16

23 Feb '16

Are you asking if there is a trademark or other intellectual property restriction on using the acronym "MPI"? If so, you should probably consult a lawyer about that. If you're asking if you can release an open source software project that contains the name "MPI", if this software has nothing to do with the Message Passing Interface as described by www.mpi-forum.org, it would be nice if you didn't. > On Feb 23, 2016, at 10:24 AM, Dorau, Lukasz <lukasz.dorau(a)intel.com> wrote: > > Hi, > > Can you tell me who is the owner of the 'MPI' acronym? > > I want to use this acronym in the name of the project that I am going to release as open source project and I would like to ask the owner if I can use it... > > Regards, > Lukasz > > > _______________________________________________ > mpi-comments mailing list > mpi-comments(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Who is the owner of the 'MPI' acronym?
by Dorau, Lukasz 23 Feb '16

23 Feb '16

Hi, Can you tell me who is the owner of the 'MPI' acronym? I want to use this acronym in the name of the project that I am going to release as open source project and I would like to ask the owner if I can use it... Regards, Lukasz

1 0

Re: [Mpi-comments] Openmpi on xilkernel
by Jeff Squyres (jsquyres) 23 Feb '16

23 Feb '16

This mailing list is for General MPI standard questions. You should probably ask on the Open MPI mailing list - see www.open-MPI.org. Sent from my phone. No type good. > On Feb 22, 2016, at 11:14 PM, Monika Hemnani <hemnanimt1(a)rknec.edu> wrote: > > Can Openmpi library be run on xilkernel(OS from Xilinx)? > If yes, how to install it on xilkernel? > _______________________________________________ > mpi-comments mailing list > mpi-comments(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments

1 0

Openmpi on xilkernel
by Monika Hemnani 22 Feb '16

22 Feb '16

Can Openmpi library be run on xilkernel(OS from Xilinx)? If yes, how to install it on xilkernel?

1 0

Re: [Mpi-comments] Bug in example 7.9 about neighbourhood collectives
by William Gropp 26 Jan '16

26 Jan '16

Thanks, Dan. Can you open an issue for this? Bill William Gropp Director, Parallel Computing Institute Thomas M. Siebel Chair in Computer Science Chief Scientist, NCSA University of Illinois Urbana-Champaign On Jan 26, 2016, at 7:59 AM, Daniel Holmes <dholmes(a)epcc.ed.ac.uk> wrote: > In Figure 7.2 (part of example 7.9, in section 7.6, page 330, line 18), the call to "MPI_DIMS_CREATE" is erroneous because the first parameter is given as "comm" rather than "comm_size". To pass "comm_size", the example would need an extra variable declaration and an extra line of code (between lines 17 and 18) that calls the "MPI_COMM_SIZE" function. > > Cheers, > Dan. > > -- > Dan Holmes > Applications Consultant in HPC Research > EPCC, The University of Edinburgh > James Clerk Maxwell Building > The Kings Buildings > Peter Guthrie Tait Road > Edinburgh > EH9 3FD > T: +44(0)131 651 3465 > E: dholmes(a)epcc.ed.ac.uk > > *Please consider the environment before printing this email.* > > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > mpi-comments mailing list > mpi-comments(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-comments

1 0

Bug in example 7.9 about neighbourhood collectives
by Daniel Holmes 26 Jan '16

26 Jan '16

In Figure 7.2 (part of example 7.9, in section 7.6, page 330, line 18), the call to "MPI_DIMS_CREATE" is erroneous because the first parameter is given as "comm" rather than "comm_size". To pass "comm_size", the example would need an extra variable declaration and an extra line of code (between lines 17 and 18) that calls the "MPI_COMM_SIZE" function. Cheers, Dan. -- Dan Holmes Applications Consultant in HPC Research EPCC, The University of Edinburgh James Clerk Maxwell Building The Kings Buildings Peter Guthrie Tait Road Edinburgh EH9 3FD T: +44(0)131 651 3465 E: dholmes(a)epcc.ed.ac.uk *Please consider the environment before printing this email.* The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

Re: [Mpi-comments] [mpiwg-p2p] Errata to MPI-3.0 and MPI-3.1 about MPI_WAIT
by Bland, Wesley 28 Dec '15

28 Dec '15

And the fix has been committed: https://github.com/mpi-forum/mpi-standard/commit/9ddd672c28c86a2abaa8fcac6b… > On Dec 28, 2015, at 8:37 AM, Thakur, Rajeev <thakur(a)mcs.anl.gov> wrote: > > This was reported before. See http://lists.mpi-forum.org/mpiwg-p2p/2015/06/0122.php > > Rajeev > > >> On Dec 28, 2015, at 5:50 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: >> >> Dear pt-2-pt WG and all, >> >> In the description of MPI_WAIT, >> MPI-3.1 page 53 line 24-25 and >> MPI-3.0 page 53 line 27-28 reads >> >> Any other type of request is >> and the request handle is set to MPI_REQUEST_NULL. >> >> but it should read >> >> Any other type of request is deallocated >> and the request handle is set to MPI_REQUEST_NULL. >> >> This corrected text was voted into MPI-3.0 through ticket 321. >> The missing "deallocated" is a "typo" probably during >> the implementation of this ticket before MPI-3.0 was published. >> >> Ticket 321: >> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/321 >> and >> https://svn.mpi-forum.org/trac/mpi-forum-web/attachment/ticket/321/ticket32… >> page 54, lines 14-18. >> >> This is a request for an erratum for MPI-3.1, >> which also applies to MPI-3.0. >> >> Best regards >> Rolf >> >> >> >> -- >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de >> 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: Room 1.307) >> _______________________________________________ >> mpiwg-p2p mailing list >> mpiwg-p2p(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-p2p > > _______________________________________________ > mpiwg-p2p mailing list > mpiwg-p2p(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-p2p

1 0