[mpiwg-tools] proposed text

Kathryn Mohror kathryn at llnl.gov
Mon Nov 24 11:32:51 CST 2014


Thanks to everyone who helped craft the text for #383. Let's hope that
this is the final iteration! I announced the ticket to the Forum mailing
list. We have until 2pm PST to make changes, so speak up now if you see
something that is incorrect.

Kathryn
_________________________________________________________________
Kathryn Mohror, kathryn at llnl.gov, http://scalability.llnl.gov/
Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA,
USA






On 11/24/14, 5:27 AM, "Jeff Squyres (jsquyres)" <jsquyres at cisco.com> wrote:

>I'm out on vacation this week and can't easily join a Webex or
>participate deeply. So if you're convinced that you can make the enum var
>*names* be equivalent and not its *values*, then I'll be happy.
>
>Regardless, I think you all understand my example/concern, so if it's not
>an issue, great. :)
>
>I'll leave it to you folks to figure out.
>
>Sent from my phone. No type good.
>
>> On Nov 24, 2014, at 6:33 AM, Michael Knobloch
>><m.knobloch at fz-juelich.de> wrote:
>> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hi all,
>> 
>> here I have to disagree with Jeff - only the important part highlighted:
>> 
>>> On 11/22/2014 02:45 PM, Jeff Squyres (jsquyres) wrote:
>>> 
>>> Enumerations ============
>>> 
>>> Yes, enumerated values must *not* be defined as equivalent.
>>> 
>>> I have a concrete example why they should not be equivalent:
>>> 
>>> - Remember that I want to use enumerated values to contain
>>> information about the underlying network - The network interface
>>> used by MPI processes on server A has network address "A.B.C.D",
>>> but the NI used by MPI processes on server B has address
>>> "W.X.Y.Z".
>> 
>> No one wants enumerated values to be equivalent - just the names of
>> enum items iff the corresponding enums are equivalent - and I think
>> that was clear from the text Kathryn sent around. So if I understand
>> your example correctly we have on both processes an enum
>> "network_info" with variable name "network_address" with the value
>> "A.B.C.D" on process A and "W.X.Y.Z" on process B. And I think this is
>> covered by our definition of having semantically the same behavior.
>> 
>> Am I'm missing a point here?
>> 
>> - -Michael
>> - --
>> Michael Knobloch
>> Institute for Advanced Simulation (IAS)
>> Jülich Supercomputing Centre (JSC)
>> Telefon: +49 2461 61-3546
>> Telefax: +49 2461 61-6656
>> E-Mail: m.knobloch at fz-juelich.de
>> Internet: http://www.fz-juelich.de/jsc
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> 
>> iQIcBAEBAgAGBQJUcxdkAAoJENAucJeJjnBJ0OsP/0mr1o1W4Jjmr98SJ43g9i2M
>> IEd6zHMf8cceS0UA9pitmg/fdMXLTGsI/HH6WIAZuznPP4cINqNPB+i2EVYKJLOn
>> saqPKwjQINQzoJZCxrNtFh7nntJlol5JCnqXt6DH1WtHy0Z3qR6B8YTDGUgPSCpN
>> Z6D///9e00WAC2EcY6djQCmRra0cGmdfz5ui9WmwUcNnzZGEynKT97pqvgcfFBhQ
>> RtdsbbO3zpWPBS8pHtQyf/Lz117eVAhqCgoIsehwiLBXJvbP7XNpmjCRBJM6miMJ
>> 0nfvLBMlZ80HRq5dBi20XwqQNEDkYSyD15XNvDNAVq6yvXksMUxqenwnbSgj2puA
>> Ti+RU3SmndkHo4hLhO6RiEHSbn0w5Bdckmvbj1IqqAelkIB/NH2X+yCsNNv7aCvB
>> jxYcnPdWa4sw+QfbEkjP1eqhvYeEWKMuwvrVOr1Ns4C/S95WiwiMCXw4f5dmUn5q
>> u6+PjZRuJVLMc0u1PBx0UmWO5Kmt0xu3C9D4X/1g5BhP2gBvydk0y7IvqeJYqQxh
>> 5+bzy0Vjzr6Ly/pp+pjP51xPeZq2q1GlzAp1l4gFnqi6zSpQDrMpnuZSxM/KuBLS
>> P3BisCJDBP4woy4nNCnRZZnPsWjhqwDpdb73RQ2tSaOK1bXt0oJRZkyJJkGc9CWR
>> R58VxGZvH9B2ppqBEUGj
>> =WPBk
>> -----END PGP SIGNATURE-----
>> 
>> 
>> 
>>-------------------------------------------------------------------------
>>-----------------------
>> 
>>-------------------------------------------------------------------------
>>-----------------------
>> Forschungszentrum Juelich GmbH
>> 52425 Juelich
>> Sitz der Gesellschaft: Juelich
>> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
>> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
>> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
>> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
>> Prof. Dr. Sebastian M. Schmidt
>> 
>>-------------------------------------------------------------------------
>>-----------------------
>> 
>>-------------------------------------------------------------------------
>>-----------------------
>> 
>> _______________________________________________
>> mpiwg-tools mailing list
>> mpiwg-tools at lists.mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
>_______________________________________________
>mpiwg-tools mailing list
>mpiwg-tools at lists.mpi-forum.org
>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tools-3.pdf
Type: application/pdf
Size: 327867 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-tools/attachments/20141124/ac123914/attachment-0001.pdf>


More information about the mpiwg-tools mailing list