> On Apr 26, 2016, at 4:33 PM, Sylvain Jeaugey wrote:
>
> Oh, I see. No, we don't want to add a full modex if there isn't one already.
>
> Now, if we restrict this to the intra-node (we don't care on which
> socket/core is a distant process), is there any simple way to do an
> intra-node-only
Oh, I see. No, we don't want to add a full modex if there isn't one already.
Now, if we restrict this to the intra-node (we don't care on which
socket/core is a distant process), is there any simple way to do an
intra-node-only modex ?
On 04/26/2016 04:28 PM, Ralph Castain wrote:
On Apr 26,
> On Apr 26, 2016, at 3:35 PM, Sylvain Jeaugey wrote:
>
> Indeed, I implied that affinity was set before MPI_Init (usually even before
> the process is launched).
>
> And yes, that would require a modex ... but I thought there was one already
> and maybe we could pack the affinity information
Indeed, I implied that affinity was set before MPI_Init (usually even
before the process is launched).
And yes, that would require a modex ... but I thought there was one
already and maybe we could pack the affinity information inside the
existing one.
On 04/26/2016 02:56 PM, Ralph Castain w
Hmmm…you mean for procs on the same node? I’m not sure how you can do it
without introducing another data exchange, and that would require the app to
execute it since otherwise we have no idea when they set the affinity.
If we assume they set the affinity prior to calling MPI_Init, then we could
Within the BTL code (and surely elsewhere), we can use those convenient
OPAL_PROC_ON_LOCAL_{NODE,SOCKET, ...} macros to figure out where another
endpoint is located compared to us.
The problem is that it only works when ORTE defines it. The NODE works
almost always since ORTE is always doing i
