[mpiwg-tools] Problem of MPI_T_PVAR_GET_INDEX

[Schulz, Martin]

Hi Junchao,

Great catch - thanks. We added the ability to have multiple variables with the same name but different classes on purpose to allow, e.g., a level, a high watermark, and a low watermark on the same resource. This still seems useful, so I don't think we should change that - adding the pvar class argument seems like the best (and also necessary) option.

Martin


On Oct 7, 2013, at 11:31 AM, Junchao Zhang <jczhang at mcs.anl.gov>
 wrote:

> I noticed there is a proposal to query cvar/pvar/category index by their name. The one for pvar is questionable: 
>   MPI_T_PVAR_GET_INDEX(name, pvar_index)
> Since the Standard reads (p577)
> 
>   Advice to implementors. Groups of variables that belong closely together, but have different classes, can have the same name. This choice is useful, e.g., to refer to multiple variables that describe a single resource (like the level, the total size, as well as high and low watermarks). (End of advice to implementors.)
> 
> It implies pvar names are not unique among pvar classes.  So we need to require unique pvar names, or add a pvar class argument to MPI_T_PVAR_GET_INDEX.
> 
> --Junchao Zhang
> _______________________________________________
> mpiwg-tools mailing list
> mpiwg-tools at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

________________________________________________________________________
Martin Schulz, schulzm at llnl.gov, http://people.llnl.gov/schulzm
CASC @ Lawrence Livermore National Laboratory, Livermore, USA