[Mpi3-rma] MPI-3.1 consideration slides

[Jim Dinan]

Hi All,

Unfortunately, I won't be able to attend the meeting this week.  I can 
join the working group sessions by phone if we are able to set something 
up.  I would like to add the following items to the working group's agenda:

MPI 3.0 errata:

https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/346
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/347
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/348
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/350

Corrections for MPI 3.next:

Shared memory window attribute query mechanism:
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/344

Dynamic window displacements:
https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/349

Thanks,
  ~Jim.

On 12/2/12 8:53 PM, Pavan Balaji wrote:
>
> Attached is a slightly updated version of the slides.  I had forgotten
> to include one additional item (in the last slide of the attached slide
> deck).
>
>   -- Pavan
>
> On 12/02/2012 09:30 AM US Central Time, Pavan Balaji wrote:
>>
>> On 12/02/2012 05:27 AM US Central Time, Torsten Hoefler wrote:
>>> The only thing I disagree to is slide 6. Win_sync really does nothing
>>> in the separate case. Your example would work on shared memory if
>>> flush issues a memory barrier *and* MPI_Barrier() is an optimization
>>> barrier (which is is in C and needs to be ensured in Fortran anyway).
>>> But we can discuss next week.
>>
>> The problem here is that MPI_BARRIER is a process barrier, not a memory
>> barrier.  FWIW, with current compilers, which do not reorder
>> instructions across functions, this should work correctly.  But this is
>> a correctness concern when compilers do more than that, e.g., IPC
>> optimizations.
>>
>> An alternative would be to leave it as-is, and add a note that we assume
>> the compiler will not reorder instructions here because it's a function
>> call, though I don't prefer this alternative.
>>
>>   -- Pavan
>>
>
>
>
> _______________________________________________
> mpi3-rma mailing list
> mpi3-rma at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma
>