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

Fence CudaUVMSpace allocations #230

Closed
hcedwar opened this issue Mar 29, 2016 · 1 comment
Closed

Fence CudaUVMSpace allocations #230

hcedwar opened this issue Mar 29, 2016 · 1 comment
Assignees
Labels
Feature Request Create new capability; will potentially require voting
Milestone

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Mar 29, 2016

Trlinos has a significant issue (trilinos/Trilinos#227) with CudaUVMSpace allocation fencing. This may be resolved by adding fences before and after View allocations in CudaUVMSpace.

@hcedwar hcedwar added the Feature Request Create new capability; will potentially require voting label Mar 29, 2016
@hcedwar hcedwar added this to the GTC 2016 milestone Mar 29, 2016
@hcedwar hcedwar self-assigned this Mar 29, 2016
hcedwar added a commit that referenced this issue Mar 29, 2016
…:View, issue #230 .

Hopefully will resolve reocurring Trilinos issue.
@crtrott
Copy link
Member

crtrott commented Apr 1, 2016

Merged to master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Create new capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

2 participants