Skip to content
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

dspaces_put_sync behavior is surprising #26

Open
philip-davis opened this issue Aug 29, 2017 · 0 comments
Open

dspaces_put_sync behavior is surprising #26

philip-davis opened this issue Aug 29, 2017 · 0 comments
Assignees

Comments

@philip-davis
Copy link
Owner

(At least in the Infiniband transport)

dspaces_put_sync completes once the ss_obj_put rpc call has been received by the server. There is no dependency on the server having completed the RDMA read. This means that, for example, the test writer will release write lock before the server has received the written object. This seems to defeat the purpose of the sync call. I think this might be due to incorrect processing of work completion events; the client seems to update the sync lock on a message completion, rather than an RDMA completion. This may point to some more subtle issues in event processing with the Infiniband transport. I'm not sure if the issue is present on GNI transport yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants