[mpiwg-tools] Open MPI pvar scheme

[Jeff Squyres (jsquyres)]

On Nov 11, 2013, at 5:34 PM, Kathryn Mohror <kathryn at llnl.gov> wrote:

>> The answer we're currently using is what we discussed on the tools call: <prefix> is a state variable with enumeration, and all <prefix><name> pvars are expected to use the mapping of that state variable.  For exmple, btl_usnic_num_sends will follow the pattern established by the btl_usnic pvar state variable.
> 
> I guess the problem with this (and maybe I'm missing something) is that it will be hard for a tool to know if a particular state variable with an enumeration describes other variables that have the prefix in their names. In other words, how do I know that this state variable is special and not just that some pvars  happen to have the same prefix, but there's no relationship between them?

I think what we're trying to say is this:

- for a given pvar category X
- if there's a state pvar Y (which therefore has an associated enumeration)
- then any pvar in category X that has a name that begins with Y is related to state pvar Y

This has the restriction that you shouldn't give a state pvar a name that is a prefix of some other pvar in the same category (i.e., so that you don't get incorrect relationship implications).

Since this convention is limited to a single category, it may not be too onerous.

-- 
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/