On Jul 31, 2014, at 3:41 PM, George Bosilca <bosilca_at_[hidden]> wrote:
> On Jul 31, 2014, at 18:26 , Jeff Squyres (jsquyres) <jsquyres_at_[hidden]> wrote:
>> George --
>> Got 2 questions for ya:
>> 1. I see some orte_* specific symbols/functions in ompi_mpi_init.c. Was that intentional? Shouldnt that stuff be in the RTE framework, or some such?
> Good catch. Fixed in r32384.
>> 2. In tracking down some stuff relating to process names, it looks like names are now setting set by ompi/proc/proc.c (i.e., it makes a call to opal_proc_local_set(...)). And this happens after the RTE is initialized. Is that right? Seems a little weird to me shouldn't the RTE be the one that sets the process names?
> In my view the RTE should stay outside any local setting of the process. The RTE role is to move the info around, not to force it on everybody else. When multiple layers will use the BTL (and thus the OPAL level proc), we will have to figure out who will be responsible for setting the data into the OPAL level proc. Meanwhile, OMPI is the only one using this proc.
Uhhhh....not exactly. The dstore and pmi frameworks depend on it, and that the name matches the one in the RTE. So ORTE is going to have to set that proc object, and I imagine STCI will too.
>> Jeff Squyres
>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
>> devel mailing list
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: http://www.open-mpi.org/community/lists/devel/2014/07/15407.php
> devel mailing list
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: http://www.open-mpi.org/community/lists/devel/2014/07/15408.php