-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared Memory Windows and MPI_MODE_NOSTORE #19
Comments
we should do 1. |
@jeffhammond To accomplish (1) in a way that's backward compatible, we would need to do (3) and introduce a new flag. I guess for MPI 4.1 we will simply do (3) and leave the new flag for a future version of the spec. |
I guess that https://github.com/mpi-forum/mpi-standard/pull/708 adds a wrinkle in this plan. @devreal How should we deal with |
Exactly 😄 I don't think there is a practical consequence to breaking backwards compatibility in the wording. I don't think anyone is optimizing out memory barriers to a degree that would be impacted by this. For example, neither MPICH nor Open-MPI does anything with NOSTORE right now. |
Same for Open MPI, AFAICS. |
If https://github.com/mpi-forum/mpi-standard/pull/708 goes in, I'd say we extend |
Another possible solution:
|
Background
The "local window" of a shared memory window is the portion allocated by the local process (Sec. 12.2.3, definition of
size
argument). A process can perform stores to both the local and non-local portions of a shared memory window.The
MPI_MODE_NOSTORE
assertion is defined as follows:Problem Statement
It may be impossible for implementations to optimize window synchronization using the
MPI_MODE_NOSTORE
flag because processes can perform stores to the non-local portions of the window.Possible Solutions
MPI_MODE_NOSTORE
for shared memory windows to cover both local and non-local window portions.MPI_MODE_NOSTORE
may not be useful with shared memory windows.MPI_MODE_NOSTORE
is ignored for shared memory windows.Proposed Solution
Add a restriction that
MPI_MODE_NOSTORE
is ignored for shared memory windows.The text was updated successfully, but these errors were encountered: