February 2014 - mpiwg-tools - mailman3.cels.anl.gov

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Kathryn Mohror 13 Feb '14

13 Feb '14

Hi all, Please have a look at this since we have to decide if it's ready for a reading, and submit it to the forum for review on Monday if we do. Kathryn On Feb 7, 2014, at 1:05 PM, "Mohror, Kathryn" <mohror1(a)llnl.gov> wrote: > Hi all, > > As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments. > > Kathryn > > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA > > > > > > > > > <tools-3.pdf>_______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Junchao Zhang 10 Feb '14

10 Feb '14

Yes, I got it that now. Thanks. --Junchao Zhang On Mon, Feb 10, 2014 at 3:36 PM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > Hi Junchao, > > > PS: I find MPI_CHAR variables are a little special. For MPI_INT like > variables, we get their count from *_handle_alloc. When we write them, very > likely we don't increase its count. But for MPI_CHAR variables, it is not > the case. When you write them, you probably have a longer string to write! > > > The count returned for MPI_CHAR variables is supposed to be long enough to > contain the largest valid value of the variable. Does that address what you > are thinking? > > Kathryn > > > > > --Junchao Zhang > > > On Sat, Feb 8, 2014 at 9:54 AM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > >> Hi Junchao, >> >> I'm not sure what you mean. MPI_CHAR is in the list of types allowed for >> variables in section 14.3.5. >> >> Kathryn >> >> On Feb 8, 2014, at 4:54 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: >> >> When to use MPI_CHAR? I don't find it in the text. >> At least, for non-generic pvars, MPI_CHAR is not in the allowed types >> currently. >> >> --Junchao Zhang >> Hi all, >> >> As we discussed in our call, I have drafted new text for ticket 405 >> which clarifies our intent for the MPI_CHAR datatype to represent strings >> in the tools interface. Please take a look at the red text for ticket 405 >> in the attached document and send your comments. >> >> Kathryn >> >> >> _________________________________________________________________ >> Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ >> Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, >> USA >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >> >> >> _________________________________________________________________ >> Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ >> Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, >> USA >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >> > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, > USA > > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >

1 0

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Kathryn Mohror 10 Feb '14

10 Feb '14

Hi Junchao, > > PS: I find MPI_CHAR variables are a little special. For MPI_INT like variables, we get their count from *_handle_alloc. When we write them, very likely we don't increase its count. But for MPI_CHAR variables, it is not the case. When you write them, you probably have a longer string to write! The count returned for MPI_CHAR variables is supposed to be long enough to contain the largest valid value of the variable. Does that address what you are thinking? Kathryn > > > > --Junchao Zhang > > > On Sat, Feb 8, 2014 at 9:54 AM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > Hi Junchao, > > I'm not sure what you mean. MPI_CHAR is in the list of types allowed for variables in section 14.3.5. > > Kathryn > > On Feb 8, 2014, at 4:54 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > >> When to use MPI_CHAR? I don't find it in the text. >> At least, for non-generic pvars, MPI_CHAR is not in the allowed types currently. >> >> --Junchao Zhang >> >> Hi all, >> >> As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments. >> >> Kathryn >> >> >> _________________________________________________________________ >> Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ >> Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA > > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Junchao Zhang 08 Feb '14

08 Feb '14

My fault. I misunderstood the text. PS: I find MPI_CHAR variables are a little special. For MPI_INT like variables, we get their count from *_handle_alloc. When we write them, very likely we don't increase its count. But for MPI_CHAR variables, it is not the case. When you write them, you probably have a longer string to write! --Junchao Zhang On Sat, Feb 8, 2014 at 9:54 AM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > Hi Junchao, > > I'm not sure what you mean. MPI_CHAR is in the list of types allowed for > variables in section 14.3.5. > > Kathryn > > On Feb 8, 2014, at 4:54 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > > When to use MPI_CHAR? I don't find it in the text. > At least, for non-generic pvars, MPI_CHAR is not in the allowed types > currently. > > --Junchao Zhang > Hi all, > > As we discussed in our call, I have drafted new text for ticket 405 > which clarifies our intent for the MPI_CHAR datatype to represent strings > in the tools interface. Please take a look at the red text for ticket 405 > in the attached document and send your comments. > > Kathryn > > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, > USA > > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, > USA > > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools >

1 0

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Kathryn Mohror 08 Feb '14

08 Feb '14

Hi Junchao, I'm not sure what you mean. MPI_CHAR is in the list of types allowed for variables in section 14.3.5. Kathryn On Feb 8, 2014, at 4:54 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > When to use MPI_CHAR? I don't find it in the text. > At least, for non-generic pvars, MPI_CHAR is not in the allowed types currently. > > --Junchao Zhang > > Hi all, > > As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments. > > Kathryn > > > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA > > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] ticket 405: MPI_CHAR as string
by Junchao Zhang 08 Feb '14

08 Feb '14

When to use MPI_CHAR? I don't find it in the text. At least, for non-generic pvars, MPI_CHAR is not in the allowed types currently. --Junchao Zhang Hi all, As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments. Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

1 0

ticket 383: variables with same name should have same meaning
by Mohror, Kathryn 07 Feb '14

07 Feb '14

Hi all, This thread is to discuss the text we want to add to clarify that implementations should strive to provide a consistent view of variables across heterogeneous environments. In other words, variables with the same name should have "the same" meaning. In our last call, we decided that the tools people need to figure out what makes sense for them and the implementors will see if they can provide what the tools people want. The current debate seems to be (from what I heard on the call): 1) If variables don't have the same exact meaning, they should have different names. 2) We should provide a high level set of variables that have the similar meanings across heterogenous environments (like the PAPI model, e.g., PAPI can report the number of floating point operations, but exactly what counts as a floating point op can vary across processor architectures). So, let's discuss! Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

ticket 405: MPI_CHAR as string
by Mohror, Kathryn 07 Feb '14

07 Feb '14

Hi all, As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments. Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] Telecon tomorrow Feb 6
by Kathryn Mohror 06 Feb '14

06 Feb '14

I put the notes from today's call on the wiki: https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/notes-2014-02-06 Kathryn On Feb 5, 2014, at 4:20 PM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > Hi all, > > This is a reminder about our regular telecon tomorrow Feb 6 at 8 AM Pacific, 11 AM Eastern. As always, the link to the webex is on the main wiki page: https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/MPI3Tools > > We plan to talk about tickets to be read at the next forum meeting to make sure they are ready and possibly continue the discussion of Marc-Andre's idea for variable consistency (realms). > > Kathryn > _________________________________________________________________ > Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ > Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA > > > > > > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Telecon tomorrow Feb 6
by Kathryn Mohror 05 Feb '14

05 Feb '14

Hi all, This is a reminder about our regular telecon tomorrow Feb 6 at 8 AM Pacific, 11 AM Eastern. As always, the link to the webex is on the main wiki page: https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/MPI3Tools We plan to talk about tickets to be read at the next forum meeting to make sure they are ready and possibly continue the discussion of Marc-Andre's idea for variable consistency (realms). Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0