-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fix issue with definition of nonblocking in One Sided Chapter #300
Comments
Originally by rsthakur on 2011-12-08 21:37:17 -0600 The way nonblocking is defined for RMA operations is: On pg 10, ln 43-44: "These operations are nonblocking: the call initiates the transfer, but the transfer may continue after the call returns." That's all it says. That doesn't prevent put from blocking to acquire a lock. |
Originally by snir on 2012-01-06 17:17:48 -0600 agree with proposed solution: discussion of example was not intended to define general semantics of non-blocking RMA |
Originally by htor on 2012-02-26 11:41:00 -0600 Implemented in the updated RMA chapter -- this issues is more like a ticket 0 change because it does not change any semantics. It only removes a confusing sentence from an example (which was non-normative anyway). |
Originally by htor on 2012-02-26 11:41:54 -0600 Attachment added: |
Originally by htor on 2012-07-17 09:17:44 -0500 Committed to approved/one-sided. Please review. Torsten |
Originally by goodell on 2012-07-17 21:32:25 -0500 Review OK as of Torsten's recent PDF sent out. |
Originally by jsquyres on 2012-07-18 09:53:05 -0500 Appears to be fully committed. Moving to "Waiting for PDF reviews". |
Originally by htor on 2011-10-24 18:50:13 -0500
Author: RMA Working Group
Description
This problem exists since MPI-2.0. Example 11.5 states that MPI_PUT may block which conflicts with the earlier definition of "nonblocking". This sentence is correct because it's only relative to the example but it's misleading users and implementers to believe that MPI_PUT is allowed to block in general.
History
None.
Proposed Solution
Possible solution: fix sentence on Page 39 Line 21, Example 11.5:
remove "or, the call MPI_WIN_LOCK may not block, while the call to MPI_PUT blocks until a lock is acquired;"
Impact on Implementations
Minor (some unusual implementations may become invalid)
Impact on Applications / Users
None.
Alternative Solutions
Entry for the Change Log
The text was updated successfully, but these errors were encountered: