[Mpi3-rma] [EXTERNAL] Re: MPI-3 UNIFIED model clarification

Jed Brown jedbrown at mcs.anl.gov
Sun Aug 4 19:38:47 CDT 2013

Pavan Balaji <balaji at mcs.anl.gov> writes:

> Sorry, wrong rule.  Here's the right one:
> "A put or accumulate must not access a target window once a load/store
> update or a put or accumulate update to another (overlapping) target
> window has started on a location in the target window, until the
> update becomes visible in the public copy of the window. Conversely, a
> store to process memory to a location in a window must not start once
> a put or accumulate update to that target window has started, until
> the put or accumulate update becomes visible in process memory. In
> both cases, the restriction applies to operations even if they access
> disjoint locations in the window."

Your example had P1 *reading* from that non-overlapping part of its own
memory.  If you change it to writing, then I see that the paragraph
above applies, and is extra overhead relative to UNIFIED.  Thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-rma/attachments/20130804/a11e9a86/attachment-0001.pgp>

More information about the mpiwg-rma mailing list