Memory Model Part Deux

[jdinan]

Summary

This ticket is a follow-on to #229 with the goal of filtering out issues that have already been addressed in OpenSHMEM 1.5 and organize memory model work for OpenSHMEM 1.6.

This issue is work in progress and not yet ready for discussion.

Open Issues

Ordering of blocking fetching operations

• Blocking gets should be unordered to support weak memory models

  • May require the addition of a new fence, fence with an argument, or extension to shmem_fence to allow users to order blocking gets

• Blocking fetching atomics are assumed to be ordered

• May want to add support for unordered fetching atomics, possibly as nonblocking APIs

Ref #233

Scope of fence operations

Ref #232

[manjugv]

Ping @jdinan @akhillanger Do you have any updates on this issue?

[akhillanger]

Manju, No update yet.
Here is a link to the two slide sets presented previously:
OpenSHMEM Memory Model Discussion at RMA Working Group Meeting June 08 2020
OpenSHMEM Memory Model Discussion F2F September 2019 SUNY