Gilles Gouaillardet 9e9261e90a pmix: correctly set locality flags in proc_flags ...

do not use opal_process_info.cpuset which is not
set at that time.

2014-12-26 15:37:08 +09:00

..

configure.m4

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00

Makefile.am

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00

pmix_native_component.c

Per the PR and discussion on today's telecon, extend the process name definition as a two-field struct of uint32_t's down to the OPAL layer. This resolves issues created by prior commits that impacted both heterogeneous and SPARC support. This also simplifies the OMPI code base by removing the need for frequent memcpy's when transitioning between the OMPI/ORTE layers and OPAL.

2014-11-11 17:00:42 -08:00

pmix_native.c

pmix: correctly set locality flags in proc_flags

2014-12-26 15:37:08 +09:00

pmix_native.h

Per the PR and discussion on today's telecon, extend the process name definition as a two-field struct of uint32_t's down to the OPAL layer. This resolves issues created by prior commits that impacted both heterogeneous and SPARC support. This also simplifies the OMPI code base by removing the need for frequent memcpy's when transitioning between the OMPI/ORTE layers and OPAL.

2014-11-11 17:00:42 -08:00

usock_sendrecv.c

Per the PR and discussion on today's telecon, extend the process name definition as a two-field struct of uint32_t's down to the OPAL layer. This resolves issues created by prior commits that impacted both heterogeneous and SPARC support. This also simplifies the OMPI code base by removing the need for frequent memcpy's when transitioning between the OMPI/ORTE layers and OPAL.

2014-11-11 17:00:42 -08:00

usock.c

Bring over some updates from the PMIx branch - mostly just minor cleanups. Make the direct grpcomm component no longer be the default. For now, we seem to be having problems with non-blocking fence operations, so make them not be the default under any scenario (e.g., when sm is the only btl in operation).

2014-09-06 19:19:44 +00:00