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

Adding support for NBI put with signal operation #238

Closed
wants to merge 13 commits into from

Conversation

naveen-rn
Copy link
Contributor

@naveen-rn naveen-rn commented Aug 8, 2018

This PR extends the #218 proposal adding non-blocking support for put-with-signal operations. The nonblocking variant of the put-with-signal operation is semantically equivalent to:

shmem_put_nbi();
shmem_fence();
shmem_put_nbi();

Following the trend of no-example for any NBI operations, there is no example added for this proposed routine in this PR. And the placement of the routine, will also be modified based on Issue #216.

Expected DOC changes:

  1. Since the change log entry framework and the keyword highlighting changes are added as part of Add support for put with signal operation #218 - there is no need to do it again in this PR. We will clean it up after reading.

@naveen-rn naveen-rn changed the title Adding support for NBI put with signal Adding support for NBI put with signal operation Aug 8, 2018
We are adding the restricy qualifier to sig_addr data objects and
expects it to not overlap or be same as the dest or source data
objects.
@naveen-rn
Copy link
Contributor Author

I had to close this PR - because the history in this branch was modified and makes it hard to maintain a separate branch for blocking and nbi-put-with-signal.
I have created #244 for continuing the prpoposal to add NBI put-with-signal

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

Successfully merging this pull request may close these issues.

1 participant