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

UnorderedMap: make it accept Devices or MemorySpaces #711

Closed
crtrott opened this issue Mar 28, 2017 · 0 comments
Closed

UnorderedMap: make it accept Devices or MemorySpaces #711

crtrott opened this issue Mar 28, 2017 · 0 comments
Assignees
Labels
Enhancement Improve existing capability; will potentially require voting

Comments

@crtrott
Copy link
Member

crtrott commented Mar 28, 2017

It is useful to tell an unordered map where to store its memory independently of the execution space. For example on KNL I might need to decide whether to put the map in HBM or DDR memory. This can be done by making the map accept Kokkos::Device instead of an execution space as the views allow.

This will automatically make it work for execution and memory spaces since both are devices as well.

I already made that change and pushed it.

@crtrott crtrott self-assigned this Mar 28, 2017
@crtrott crtrott added the Enhancement Improve existing capability; will potentially require voting label Mar 28, 2017
@crtrott crtrott added this to the 2017-April-end milestone Mar 28, 2017
@crtrott crtrott closed this as completed Apr 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

1 participant