Yeah; the cid needs to be unique from the communicator passed to win_create
because the win functions will call collectives on their communicator. It
would be unfortunate to have user collectives and window collectives colliding
(unfortunate meaning violating the standard here). It just makes
RIght, my mistake, I missed the new cid generation in the comm duplicator
calls. Thanks a lot!
--
Abhisek
Live Long and Prosper
On Mon, Aug 31, 2015 at 9:25 AM, Todd Kordenbrock
wrote:
> Hi Abhisek,
>
> Both the portals4 and pt2pt OSC components call ompi_comm_dup() near the
> beginning of co
Hi Abhisek,
Both the portals4 and pt2pt OSC components call ompi_comm_dup() near the
beginning of component_select(), so each window has it's own communicator.
The duplicated communicator has a unique contextid and therefore the window
has unique match bits/hash key.
Thanks,
todd
On Mon, Aug 3
On Aug 27, 2015, at 11:55 AM, abhisek...@gmail.com wrote:
>
> I want to know if it is allowed in MPI one-sided communication to open
> multiple windows simultaneously using the same communicator.
Yes.
> The standard does not seem to forbid it as far as I can see, but when I look
> at the ope
Hi,
I want to know if it is allowed in MPI one-sided communication to open
multiple windows simultaneously using the same communicator.
The standard does not seem to forbid it as far as I can see, but when I
look at the open mpi osc components (rdma and portals4) it looks like a
window is alway
