How is this not a no-op implementation for MPI_COMM_SELF? All you need to support is load-store on local memory, no?
We also need to support all of the RMA communication and synchronization operations. This is not an overly complex or large task, it's just currently lower priority that others. That said, if shared memory window support in ch3:sock is something that would prevent you or anyone else from using MPI 3.0 RMA, please speak up and I'll make it higher priority.
I recant my previous statement on account of ignorance and because I don't use ch3:sock and prefer you not worry about this. It's not like PETSc is using MPI_WIN_ALLOCATE_SHARED right now anyways. Jeff -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute [email protected] / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond