[Mpi3-rma] RMA op compatibility matrix
dinan at mcs.anl.gov
Fri Oct 14 16:33:15 CDT 2011
Rule #3 on page 365 of semantics and correctness:
3. A put or accumulate must not access a target window once a local
update or a put or accumulate update to another (overlapping) target
window have started on a location in the target window, until the update
becomes visible in the public copy of the window. Conversely, a local
update in 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.
A program is erroneous if it violates these rules.
PS- This rule is like five rules. We really should regroup once the
ticket is accepted and see if it can be split into a few smaller, easier
to digest rules.
On 10/14/11 3:18 PM, Pavan Balaji wrote:
> Why are they incompatible in MPI-2?
> Pavan Balaji @ iPhone
> (Big fingers. Small email.)
> On Oct 14, 2011, at 11:18 AM, James Dinan<dinan at mcs.anl.gov> wrote:
>> In MPI-2, the are not compatible, but in MPI-3, it's ok as long as there is no overlap. I've attached an updated PDF with both MPI-2 and MPI-3 tables.
>> On 10/14/11 2:02 AM, Pavan Balaji wrote:
>>> There seem to be a few errors here: load + Put/Acc and store + Get
>>> should be NOVL.
>>> -- Pavan
>>> On 10/10/2011 02:35 PM, James Dinan wrote:
>>>> Hi All,
>>>> We discussed creating a table that shows compatibility between
>>>> concurrent RMA operations. A rough mockup of this table is attached.
>>>> mpi3-rma mailing list
>>>> mpi3-rma at lists.mpi-forum.org
More information about the mpiwg-rma