October 2010 - Mpi3-bwcompat - mailman3.cels.anl.gov

Re: [Mpi3-bwcompat] Ticket 224 updated
by unknown＠example.com 07 Oct '10

07 Oct '10

Looks good to me! On Oct 6, 2010, at 8:37 PM, Fab Tillier wrote: > Hi Folks, > > Could someone with more experience in Fortran (i.e. any experience at all) please look at examples 5.15, 5.21, 13.9.2 and validate that I fixed them properly? I have no idea how you declare variables in Fortran... > > Other than that, the ticket is complete as far as I know. Let me know if you see issues. > > Thanks! > -Fab > > _______________________________________________ > Mpi3-bwcompat mailing list > Mpi3-bwcompat_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Ticket 224 updated
by unknown＠example.com 06 Oct '10

06 Oct '10

Hi Folks, Could someone with more experience in Fortran (i.e. any experience at all) please look at examples 5.15, 5.21, 13.9.2 and validate that I fixed them properly? I have no idea how you declare variables in Fortran... Other than that, the ticket is complete as far as I know. Let me know if you see issues. Thanks! -Fab

1 0

Re: [Mpi3-bwcompat] MPI Backward Compatibility Working Group
by unknown＠example.com 05 Oct '10

05 Oct '10

On Oct 5, 2010, at 11:43 AM, Solt, David George wrote: >> A different day. > > Don't you have some fancy website that does all the work for us and picks a good time? Sure; I setup a web poll for the week of Oct 18. Answer this poll with "in general" in your mind -- like "in general, I can attend at 8am US Eastern time on Mondays" (even if you have a specific conflict in the week of Oct 18): http://www.doodle.com/epimhhs43n7w89a9 -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [Mpi3-bwcompat] MPI Backward Compatibility Working Group
by unknown＠example.com 05 Oct '10

05 Oct '10

> BTW, why are we using a ginormous CC list rather than the listserv address? That would be my fault and have something to do with replying to my outlook meeting which had individual e-mails stored for some unknown reason. > A different day. Don't you have some fancy website that does all the work for us and picks a good time? Dave -----Original Message----- From: Jeff Squyres [mailto:jsquyres_at_[hidden]] Sent: Tuesday, October 05, 2010 10:38 AM To: Quincey Koziol Cc: Solt, David George; Alexander Supalov; Fab Tillier; Graham, Richard L.; William Gropp; Terry Dontje; Darius Buntinas; Dave Goodell; Torsten Hoefler; MPI-3 backwards compatability WG Subject: Re: MPI Backward Compatibility Working Group We could pick a different day. BTW, why are we using a ginormous CC list rather than the listserv address? On Oct 5, 2010, at 11:24 AM, Quincey Koziol wrote: > > On Oct 5, 2010, at 10:04 AM, Solt, David George wrote: > >> I can do 9 PDT as long as we shift a week (for example, if our first meeting at this time was Oct 22). I don't want to mess up the regular attendees though, so only if it is not an issue for Quincey, Terry and Jeff. > > Hmm, 9PDT doesn't work for me, I've got a weekly meeting at that time. I can usually go to 8PDT or 10PDT though. > > Quincey > >> Thanks, >> Dave >> >> -----Original Message----- >> From: Supalov, Alexander [mailto:alexander.supalov_at_[hidden]] >> Sent: Tuesday, October 05, 2010 7:18 AM >> To: Fab Tillier; Solt, David George; Graham, Richard L.; Quincey Koziol; William Gropp; Terry D. Dontje; Jeff Squyres; Darius Buntinas; Dave Goodell; 'Torsten Hoefler' >> Subject: RE: MPI Backward Compatibility Working Group >> >> Thanks. 9 am PDT could work for me, too. >> >> -----Original Message----- >> From: Fab Tillier [mailto:ftillier_at_[hidden]] >> Sent: Friday, October 01, 2010 5:32 PM >> To: Supalov, Alexander; Solt, David George; Graham, Richard L.; Quincey Koziol; William Gropp; Terry D. Dontje; Jeff Squyres; Darius Buntinas; Dave Goodell; 'Torsten Hoefler' >> Subject: RE: MPI Backward Compatibility Working Group >> >> Hi Alexander, >> >> Supalov, Alexander wrote on Fri, 1 Oct 2010 at 01:56:00 >> >>> Hi, >>> >>> Have been watching this intently, but the new slot is way too late (7 >>> pm Friday) for me to attend regularly. We had an earlier slot in the >>> past. Why did this change? >> >> I can't make the 7AM meetings, it conflicts with getting the kids fed and off to school. >> >> I can certainly do 9AM if that would help in the future. >> >> -Fab >> >>> >>> Best regards. >>> >>> Alexander >>> >>> -----Original Message----- >>> From: Solt, David George [mailto:david.solt_at_[hidden]] >>> Sent: Thursday, September 30, 2010 10:58 PM >>> To: Supalov, Alexander; Graham, Richard L.; Quincey Koziol; William >>> Gropp; Terry D. Dontje; Jeff Squyres; Darius Buntinas; Dave Goodell; >>> 'Torsten Hoefler'; 'ftillier_at_[hidden]' >>> Subject: MPI Backward Compatibility Working Group >>> >>> We are meeting tomorrow. It is our last scheduled meeting before >>> Chicago, so hopefully it will be productive. Until MPI_Count is signed >>> off, it is our focus for now. You may want to look over the MPI_Count >>> ticket (https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/224) if you >>> haven't already been watching it. >>> >>> Thanks, >>> Dave >> -------------------------------------------------------------------------------------- >> Intel GmbH >> Dornacher Strasse 1 >> 85622 Feldkirchen/Muenchen, Deutschland >> 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 a.M. (BLZ 502 109 00) 600119052 >> > -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [Mpi3-bwcompat] MPI_Size and non-count int parameters
by unknown＠example.com 05 Oct '10

05 Oct '10

For MPI_Type_create_struct, I really think that int is the correct type for a count. When we want to store some arbitrary integer value on a computer, we use an int to do that. To start saying that we expect structures to have so many fields that they won't fit into an int, then I think we are basically saying that int is useless and should never be used anywhere. When that is the case, its int's fault for not being large enough to hold anything useful, not our fault. The other argument is that I think MPI_Size was supposed to be a number of bytes, which wouldn't fit the use here. MPI_Type_get_envelope.... I think this should be easy. Is there any datatype creation call to create MYTYPE such that MPI_Type_get_envelope(MYTYPE,...) could possibly cause one of the 3 output's to overflow. If you look at the list of possible values for ni, na and nd (i.e max_integers, max_addresses, max_datatypes), these are often constants, but sometimes are dynamic, such as: If combiner is MPI_COMBINER_INDEXED then ni = 2*count+1. If we look at MPI_Type_indexed, we see that count is only an int, so this case does not require max_integers to be anything but an int. But we have to look at every case... If combiner is MPI_COMBINER_HINDEXED_INTEGER or MPI_COMBINER_HINDEXED than ni = count+1, na = count, but count for both of these routines is also an int. If combiner is MPI_COMBINER_INDEXED_BLOCK then ni = count+2, but count for this routine is an int. If combiner is MPI_COMBINER_STRUCT_INTEGER or MPI_COMBINER_STRUCT then ni = count+1, na = count, nd = count, which I recommend count=int in this case. If combiner is MPI_COMBINER_SUBARRAY then ni = 3*ndims+2. Ndims is an int. If combiner is MPI_COMBINER_DARRAY then ni = 4*ndims+4. Ndims is an int. So in all cases where these values are not constants, they are formed from datatype creation functions taking int's in the associated parameter location. Dave -----Original Message----- From: mpi3-bwcompat-bounces_at_[hidden] [mailto:mpi3-bwcompat-bounces_at_[hidden]] On Behalf Of Fab Tillier Sent: Tuesday, October 05, 2010 12:00 AM To: MPI-3 backwards compatability WG Subject: [Mpi3-bwcompat] MPI_Size and non-count int parameters Should MPI_Size be used where one would likely use size_t? For example, MPI_Type_create_struct (page 86), should the count parameter be MPI_Size? Likewise, should the three integers output by MPI_Type_get_envelope (page 105) be MPI_Size? Or is this yet another distinct type, and if so, should we try to cover it in this ticket? Thanks, -Fab _______________________________________________ Mpi3-bwcompat mailing list Mpi3-bwcompat_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat

1 0

MPI_Size and non-count int parameters
by unknown＠example.com 05 Oct '10

05 Oct '10

Should MPI_Size be used where one would likely use size_t? For example, MPI_Type_create_struct (page 86), should the count parameter be MPI_Size? Likewise, should the three integers output by MPI_Type_get_envelope (page 105) be MPI_Size? Or is this yet another distinct type, and if so, should we try to cover it in this ticket? Thanks, -Fab

1 0