[mpiwg-rma] same_op_no_op

[Jim Dinan]

You can't use replace and sum concurrently at a given target address.

 ~Jim.

On Mon, Mar 10, 2014 at 4:30 PM, Jeff Hammond <jeff.science at gmail.com>wrote:

> Given the following, how do I use MPI_NO_OP, MPI_REPLACE and MPI_SUM
> in accumulate/atomic operations in a standard-compliant way?
>
> accumulate_ops -- if set to same_op, the implementation will assume
> that all concurrent accumulate calls to the same target address will
> use the same operation. If set to same_op_no_op, then the
> implementation will assume that all concurrent accumulate calls to the
> same target address will use the same operation or MPI_NO_OP. This can
> eliminate the need to protect access for certain operation types where
> the hardware can guarantee atomicity. The default is same_op_no_op.
>
> We discuss this before and the resolution was not satisfying to me.
>
> Thanks,
>
> Jeff
>
> --
> Jeff Hammond
> jeff.science at gmail.com
> _______________________________________________
> mpiwg-rma mailing list
> mpiwg-rma at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-rma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-rma/attachments/20140310/adc1cd8d/attachment-0001.html>