[mpiwg-tools] working group depository

Jeff Squyres (jsquyres) jsquyres at cisco.com
Fri Apr 18 08:15:08 CDT 2014


Fix a minor typo and remove a redundant word.  To repeat -- this is a new suggestion for ticket 383 (http://svn.mpi-forum.org/trac/mpi-forum-web/ticket/383):

-----
Variables with the same name in connected processes are required to:

* Adhere to the same definition from the MPI implementation
* Exhibit the same behavioral semantics
* Return the same INOUT and OUT values from the relevant
  MPI_T_*_GET_INFO function, with the exception that OUT index values
  may differ between processes

Similarly, enumerations and categories with the same name in connected
processes must also obey the above restrictions.

Advice to implementors. The intent of these requirements is to enforce
  consistent meanings of variables, categories, and enumerations
  across connected processes.  For example, variables describing the
  number of packets sent across different network device types should
  have different names to reflect their potentially different
  meanings. (End of advice to implementors.)
-----


On Apr 17, 2014, at 6:38 PM, Jeff Squyres <jsquyres at cisco.com> wrote:

> How's this for a new suggestion:
> 
> -----
> Variables with the same name in connected processes are required to:
> 
> * Adhere to the same definition from the MPI implementation
> * Exhibit the same behavioral semantics
> * Return the same INOUT and OUT values from the relevant
>  MPI_T_*_GET_INFO function, with the exception that OUT index values
>  may differ between different processes
> 
> Similarly, enumerations and categories with the same name in connected
> processes must also obey the above restrictions,
> 
> Advice to implementors. The intent of these requirements is to enforce
>  consistent meanings of variables, categories, and enumerations
>  across connected processes.  For example, variables describing the
>  number of packets sent across different network device types should
>  have different names to reflect their potentially different
>  meanings. (End of advice to implementors.)
> -----
> 
> 
> On Apr 17, 2014, at 1:35 PM, Kathryn Mohror <kathryn at llnl.gov> wrote:
> 
>> Hi all,
>> 
>> For anyone who wanted to muck with the text for ticket 383, I put the document into the tools working group repository (trunk/working-groups/mpi-3/tools/MPI-3.1-toolsWG). 
>> 
>> Kathryn
>> _________________________________________________________________
>> Kathryn Mohror, kathryn at llnl.gov, http://scalability.llnl.gov/
>> Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> mpiwg-tools mailing list
>> mpiwg-tools at lists.mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
> 
> 
> -- 
> Jeff Squyres
> jsquyres at cisco.com
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
> 


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




More information about the mpiwg-tools mailing list