August 2013 - mpiwg-tools - mailman3.cels.anl.gov

Re: [mpiwg-tools] pvar attribute questions
by Mohror, Kathryn 30 Aug '13

30 Aug '13

Adding Martin's comment since he can't post currently. BTW, I could not understand why a pvar may be writable (i.e., not readonly) from the user? Could someone give me an example. You may want to reset the variable to its starting value so that you can measure it during a specific time period. I can't think of an example off the top of my head for using pvar_write on a variable. (Maybe setting to 0?) If I remember right, we included it for generality. If you don't want to allow a tool to write to a variable, you can just return MPI_T_ERR_PVAR_NO_WRITE. Actually, high watermarks could be a great example here: it would actually be interesting to measure the high watermark of resources like UMQ between two MPI calls. For this you would have to reset (i.e., write) the counter after every MPI call and then you can just read it before every call. The counter could still be continuous, though. Martin Kathryn On Fri, Aug 30, 2013 at 5:11 PM, Mohror, Kathryn <mohror1(a)llnl.gov<mailto:[email protected]>> wrote: Hi Martin and Junchao, Sorry, I can't respond to the list at the moment (LOFT settings) and I was trying to answer when Kathryn was sending her answer - feel free to repost on the list if it makes sense. Okay, I'm cc'ing the list so others benefit from your point. I agree with her interpretation - that was our intention. I agree, though, that probably doesn't make sense and hence I generally don't expect MPI implementations to offer high/low watermarks as non-continnous variables, but that's up to them. It could make sense though. You could possibly have a non-continuous variable that is the high watermark of some metric (e.g., messages in the unexpected queue) so that you could query it for specific time periods. But, you're right, it's up to the implementation to decide what is offered. Kathryn Martin On Aug 30, 2013, at 11:48 PM, "Mohror, Kathryn" <mohror1(a)llnl.gov<mailto:[email protected]>> wrote: Hi Junchao, I'm trying to understand MPI3 MPI_T performance variables (pvar). The standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK etc), and continuous pvars, readonly pvars.I was wondering if there is any relevance between these concepts. The standard doesn't say that. For instance, for a highwatermark pvar, I guess it should be continuous. Otherwise, suppose a pvar session starts this pvar, then stops it, and then restarts it. How can I keep track of this pvar? Let's say during the live period of the pvar, the high watermark is 50. After the pvar is stopped, it went up to as high as 90 (since it may be alive in other pvar sessions). So, when I restart the pvar, what value should I read? If a variable is not continuous then its value is not updated when it is stopped. So in your example the value would be 50 in the session that stopped the variable and 90 in any sessions that still had the variable live at the time it reached that value. There's a bit more explanation on page 579 starting at line 21. Does that help? Kathryn Thanks --Junchao Zhang _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] pvar attribute questions
by Mohror, Kathryn 30 Aug '13

30 Aug '13

Hi Junchao, If the pvar is restarted by the first session, what will be read into this pvar? I think it is 90. But this value of high watermark did not happen in the live period of the pvar in the first session. So the value 90 doesn't make sense. It should be 50, because the value of the variable is not updated when it is stopped. I don't know how to let a watermark pvar show different values in different sessions. For COUNTER, TIMER, AGGREGATE pvars, I know we can compute delta between current value and start value. But for watermark pvars, the approach does not apply. I suppose it depends on how you implement it. If it doesn't make sense in your implementation, you don't need to expose watermark variables that are non-continuous. BTW, I could not understand why a pvar may be writable (i.e., not readonly) from the user? Could someone give me an example. You may want to reset the variable to its starting value so that you can measure it during a specific time period. I can't think of an example off the top of my head for using pvar_write on a variable. (Maybe setting to 0?) If I remember right, we included it for generality. If you don't want to allow a tool to write to a variable, you can just return MPI_T_ERR_PVAR_NO_WRITE. Kathryn On Fri, Aug 30, 2013 at 5:11 PM, Mohror, Kathryn <mohror1(a)llnl.gov<mailto:[email protected]>> wrote: Hi Martin and Junchao, Sorry, I can't respond to the list at the moment (LOFT settings) and I was trying to answer when Kathryn was sending her answer - feel free to repost on the list if it makes sense. Okay, I'm cc'ing the list so others benefit from your point. I agree with her interpretation - that was our intention. I agree, though, that probably doesn't make sense and hence I generally don't expect MPI implementations to offer high/low watermarks as non-continnous variables, but that's up to them. It could make sense though. You could possibly have a non-continuous variable that is the high watermark of some metric (e.g., messages in the unexpected queue) so that you could query it for specific time periods. But, you're right, it's up to the implementation to decide what is offered. Kathryn Martin On Aug 30, 2013, at 11:48 PM, "Mohror, Kathryn" <mohror1(a)llnl.gov<mailto:[email protected]>> wrote: Hi Junchao, I'm trying to understand MPI3 MPI_T performance variables (pvar). The standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK etc), and continuous pvars, readonly pvars.I was wondering if there is any relevance between these concepts. The standard doesn't say that. For instance, for a highwatermark pvar, I guess it should be continuous. Otherwise, suppose a pvar session starts this pvar, then stops it, and then restarts it. How can I keep track of this pvar? Let's say during the live period of the pvar, the high watermark is 50. After the pvar is stopped, it went up to as high as 90 (since it may be alive in other pvar sessions). So, when I restart the pvar, what value should I read? If a variable is not continuous then its value is not updated when it is stopped. So in your example the value would be 50 in the session that stopped the variable and 90 in any sessions that still had the variable live at the time it reached that value. There's a bit more explanation on page 579 starting at line 21. Does that help? Kathryn Thanks --Junchao Zhang _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] pvar attribute questions
by Junchao Zhang 30 Aug '13

30 Aug '13

If the pvar is restarted by the first session, what will be read into this pvar? I think it is 90. But this value of high watermark did not happen in the live period of the pvar in the first session. So the value 90 doesn't make sense. I don't know how to let a watermark pvar show different values in different sessions. For COUNTER, TIMER, AGGREGATE pvars, I know we can compute delta between current value and start value. But for watermark pvars, the approach does not apply. BTW, I could not understand why a pvar may be writable (i.e., not readonly) from the user? Could someone give me an example. On Fri, Aug 30, 2013 at 5:11 PM, Mohror, Kathryn <mohror1(a)llnl.gov> wrote: > Hi Martin and Junchao, > > Sorry, I can't respond to the list at the moment (LOFT settings) and I > was trying to answer when Kathryn was sending her answer - feel free to > repost on the list if it makes sense. > > > Okay, I'm cc'ing the list so others benefit from your point. > > I agree with her interpretation - that was our intention. I agree, > though, that probably doesn't make sense and hence I generally don't expect > MPI implementations to offer high/low watermarks as non-continnous > variables, but that's up to them. > > > It could make sense though. You could possibly have a non-continuous > variable that is the high watermark of some metric (e.g., messages in the > unexpected queue) so that you could query it for specific time periods. > But, you're right, it's up to the implementation to decide what is offered. > > Kathryn > > > Martin > > > > On Aug 30, 2013, at 11:48 PM, "Mohror, Kathryn" <mohror1(a)llnl.gov> > wrote: > > Hi Junchao, > > I'm trying to understand MPI3 MPI_T performance variables (pvar). The > standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK > etc), and continuous pvars, readonly pvars.I was wondering if there is any > relevance between these concepts. The standard doesn't say that. > > For instance, for a highwatermark pvar, I guess it should be continuous. > Otherwise, suppose a pvar session starts this pvar, then stops it, and then > restarts it. How can I keep track of this pvar? Let's say during the live > period of the pvar, the high watermark is 50. After the pvar is stopped, it > went up to as high as 90 (since it may be alive in other pvar sessions). > So, when I restart the pvar, what value should I read? > > > If a variable is not continuous then its value is not updated when it is > stopped. So in your example the value would be 50 in the session that > stopped the variable and 90 in any sessions that still had the variable > live at the time it reached that value. There's a bit more explanation on > page 579 starting at line 21. Does that help? > > Kathryn > > > Thanks > --Junchao Zhang > > _______________________________________________ > 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://people.llnl.gov/mohror1 > CASC @ 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://people.llnl.gov/mohror1 > CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA > > > > >

1 0

Re: [mpiwg-tools] pvar attribute questions
by Junchao Zhang 30 Aug '13

30 Aug '13

If the pvar is restarted by the first session, what will be read into this pvar? I think it is 90. But this value of high watermark did not happen in the live period of the pvar in the first session. So the value 90 doesn't make sense. I don't know how to let a watermark pvar show different values in different sessions. For COUNTER, TIMER, AGGREGATE pvars, I know we can compute delta between current value and start value. But for watermark pvars, the approach does not apply. On Fri, Aug 30, 2013 at 4:48 PM, Mohror, Kathryn <mohror1(a)llnl.gov> wrote: > Hi Junchao, > > I'm trying to understand MPI3 MPI_T performance variables (pvar). The > standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK > etc), and continuous pvars, readonly pvars.I was wondering if there is any > relevance between these concepts. The standard doesn't say that. > > For instance, for a highwatermark pvar, I guess it should be continuous. > Otherwise, suppose a pvar session starts this pvar, then stops it, and then > restarts it. How can I keep track of this pvar? Let's say during the live > period of the pvar, the high watermark is 50. After the pvar is stopped, it > went up to as high as 90 (since it may be alive in other pvar sessions). > So, when I restart the pvar, what value should I read? > > > If a variable is not continuous then its value is not updated when it is > stopped. So in your example the value would be 50 in the session that > stopped the variable and 90 in any sessions that still had the variable > live at the time it reached that value. There's a bit more explanation on > page 579 starting at line 21. Does that help? > > Kathryn > > > Thanks > --Junchao Zhang > > _______________________________________________ > 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://people.llnl.gov/mohror1 > CASC @ 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 > -- Junchao Zhang

1 0

Re: [mpiwg-tools] pvar attribute questions
by Mohror, Kathryn 30 Aug '13

30 Aug '13

Hi Martin and Junchao, Sorry, I can't respond to the list at the moment (LOFT settings) and I was trying to answer when Kathryn was sending her answer - feel free to repost on the list if it makes sense. Okay, I'm cc'ing the list so others benefit from your point. I agree with her interpretation - that was our intention. I agree, though, that probably doesn't make sense and hence I generally don't expect MPI implementations to offer high/low watermarks as non-continnous variables, but that's up to them. It could make sense though. You could possibly have a non-continuous variable that is the high watermark of some metric (e.g., messages in the unexpected queue) so that you could query it for specific time periods. But, you're right, it's up to the implementation to decide what is offered. Kathryn Martin On Aug 30, 2013, at 11:48 PM, "Mohror, Kathryn" <mohror1(a)llnl.gov<mailto:[email protected]>> wrote: Hi Junchao, I'm trying to understand MPI3 MPI_T performance variables (pvar). The standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK etc), and continuous pvars, readonly pvars.I was wondering if there is any relevance between these concepts. The standard doesn't say that. For instance, for a highwatermark pvar, I guess it should be continuous. Otherwise, suppose a pvar session starts this pvar, then stops it, and then restarts it. How can I keep track of this pvar? Let's say during the live period of the pvar, the high watermark is 50. After the pvar is stopped, it went up to as high as 90 (since it may be alive in other pvar sessions). So, when I restart the pvar, what value should I read? If a variable is not continuous then its value is not updated when it is stopped. So in your example the value would be 50 in the session that stopped the variable and 90 in any sessions that still had the variable live at the time it reached that value. There's a bit more explanation on page 579 starting at line 21. Does that help? Kathryn Thanks --Junchao Zhang _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] pvar attribute questions
by Mohror, Kathryn 30 Aug '13

30 Aug '13

Hi Junchao, I'm trying to understand MPI3 MPI_T performance variables (pvar). The standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK etc), and continuous pvars, readonly pvars.I was wondering if there is any relevance between these concepts. The standard doesn't say that. For instance, for a highwatermark pvar, I guess it should be continuous. Otherwise, suppose a pvar session starts this pvar, then stops it, and then restarts it. How can I keep track of this pvar? Let's say during the live period of the pvar, the high watermark is 50. After the pvar is stopped, it went up to as high as 90 (since it may be alive in other pvar sessions). So, when I restart the pvar, what value should I read? If a variable is not continuous then its value is not updated when it is stopped. So in your example the value would be 50 in the session that stopped the variable and 90 in any sessions that still had the variable live at the time it reached that value. There's a bit more explanation on page 579 starting at line 21. Does that help? Kathryn Thanks --Junchao Zhang _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov<mailto:[email protected]>, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Fwd: pvar attribute questions
by Junchao Zhang 30 Aug '13

30 Aug '13

Hello, I'm trying to understand MPI3 MPI_T performance variables (pvar). The standard defines pvar sessions, pvar classes (e.g.,COUNTER, HIGHWATERMARK etc), and continuous pvars, readonly pvars.I was wondering if there is any relevance between these concepts. The standard doesn't say that. For instance, for a highwatermark pvar, I guess it should be continuous. Otherwise, suppose a pvar session starts this pvar, then stops it, and then restarts it. How can I keep track of this pvar? Let's say during the live period of the pvar, the high watermark is 50. After the pvar is stopped, it went up to as high as 90 (since it may be alive in other pvar sessions). So, when I restart the pvar, what value should I read? Thanks --Junchao Zhang

1 0

Re: [mpiwg-tools] Tools WG webex tomorrow!
by Schulz, Martin 28 Aug '13

28 Aug '13

Too late anyway, but I do like the new version. Looks good to me. Martin On Aug 27, 2013, at 10:27 PM, "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> wrote: > Shirley. > > On Aug 27, 2013, at 4:26 PM, Kathryn Mohror <kathryn(a)llnl.gov> > wrote: > >> For the reset case, how about this text addition: >> >> (even if there are no valid handles or all are read-only) >> >> Kathryn >> >> On Aug 27, 2013, at 1:23 PM, Kathryn Mohror <kathryn(a)llnl.gov> >> wrote: >> >>> Okay, I'll update the text on the ticket. I like this wording better. >>> >>> Kathryn >>> >>> On Aug 27, 2013, at 1:18 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>> >>>> I have a better suggestion (sorry... this is what happens at the last second...): >>>> >>>> Current from Kathryn's PDF: >>>> >>>> If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous variables. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified. >>>> >>>> Jeff's suggestion (delete the new sentence and add the text in ***): >>>> >>>> If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully (even if there are no non-continuous variables to be started), otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified. >>>> >>>> >>>> >>>> >>>> On Aug 27, 2013, at 12:09 PM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: >>>> >>>>> I made a ticket for this (#391) and uploaded a pdf with the proposed changes (also attached). >>>>> >>>>> Is anyone opposed to putting this up for a reading as errata? >>>>> >>>>> Kathryn >>>>> >>>>> >>>>> On Aug 27, 2013, at 5:14 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>>>> >>>>>> On Aug 26, 2013, at 7:23 PM, "Schulz, Martin" <schulz6(a)llnl.gov> wrote: >>>>>> >>>>>>>> I am now on the SUCCESS side of the fence. Does it need to be clarified as an errata? I would suggest (from 3.0 clean doc): >>>>>> >>>>>> Just to be totally clear: I don't really care which way it goes. I just saw this issue as an ambiguity that should be resolved. >>>>>> >>>>>>>> page 580, line 41: >>>>>>>> In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if no handles are valid for session and MPI_T_PVAR_ALL_HANDLES is passed in handle. >>>>>>> >>>>>>> Hmm - I fear we would have to be even more explicit: MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous (read only for reset) variables. >>>>>> >>>>>> +1. >>>>>> >>>>>> -- >>>>>> Jeff Squyres >>>>>> jsquyres(a)cisco.com >>>>>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>>>>> >>>>>> _______________________________________________ >>>>>> 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://people.llnl.gov/mohror1 >>>>> CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA >>>>> >>>>> >>>>> >>>>> >>>>> <tools-3.pdf> >>>> >>>> >>>> -- >>>> Jeff Squyres >>>> jsquyres(a)cisco.com >>>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>>> >>>> _______________________________________________ >>>> 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://people.llnl.gov/mohror1 >>> CASC @ 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://people.llnl.gov/mohror1 >> CASC @ 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 > > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

1 0

Today is the last day to make changes to the tickets!
by Kathryn Mohror 27 Aug '13

27 Aug '13

Hi all, We need to send out our intention to read the tickets today. I request all comments and changes be made/discussed by 5:00 PDT so I can send them out. Also, there is a new errata ticket #391 that we will read. So, please look at that one if you haven't already. So get reading now if you want to provide input! (Note that attached to each ticket is the correct pdf for that ticket only.) I attached the current version of the chapter to this email which is current for all tickets. Kathryn ______________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://people.llnl.gov/mohror1 CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] Tools WG webex tomorrow!
by Jeff Squyres (jsquyres) 27 Aug '13

27 Aug '13

Shirley. On Aug 27, 2013, at 4:26 PM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: > For the reset case, how about this text addition: > > (even if there are no valid handles or all are read-only) > > Kathryn > > On Aug 27, 2013, at 1:23 PM, Kathryn Mohror <kathryn(a)llnl.gov> > wrote: > >> Okay, I'll update the text on the ticket. I like this wording better. >> >> Kathryn >> >> On Aug 27, 2013, at 1:18 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >> >>> I have a better suggestion (sorry... this is what happens at the last second...): >>> >>> Current from Kathryn's PDF: >>> >>> If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous variables. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified. >>> >>> Jeff's suggestion (delete the new sentence and add the text in ***): >>> >>> If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully (even if there are no non-continuous variables to be started), otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified. >>> >>> >>> >>> >>> On Aug 27, 2013, at 12:09 PM, Kathryn Mohror <kathryn(a)llnl.gov> wrote: >>> >>>> I made a ticket for this (#391) and uploaded a pdf with the proposed changes (also attached). >>>> >>>> Is anyone opposed to putting this up for a reading as errata? >>>> >>>> Kathryn >>>> >>>> >>>> On Aug 27, 2013, at 5:14 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>>> >>>>> On Aug 26, 2013, at 7:23 PM, "Schulz, Martin" <schulz6(a)llnl.gov> wrote: >>>>> >>>>>>> I am now on the SUCCESS side of the fence. Does it need to be clarified as an errata? I would suggest (from 3.0 clean doc): >>>>> >>>>> Just to be totally clear: I don't really care which way it goes. I just saw this issue as an ambiguity that should be resolved. >>>>> >>>>>>> page 580, line 41: >>>>>>> In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if no handles are valid for session and MPI_T_PVAR_ALL_HANDLES is passed in handle. >>>>>> >>>>>> Hmm - I fear we would have to be even more explicit: MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous (read only for reset) variables. >>>>> >>>>> +1. >>>>> >>>>> -- >>>>> Jeff Squyres >>>>> jsquyres(a)cisco.com >>>>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>>>> >>>>> _______________________________________________ >>>>> 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://people.llnl.gov/mohror1 >>>> CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA >>>> >>>> >>>> >>>> >>>> <tools-3.pdf> >>> >>> >>> -- >>> Jeff Squyres >>> jsquyres(a)cisco.com >>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>> >>> _______________________________________________ >>> 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://people.llnl.gov/mohror1 >> CASC @ 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://people.llnl.gov/mohror1 > CASC @ 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 -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0