Skip to content

Move _memory submodule directly under dpctl #120

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.

Sign up for GitHub

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

Jump to bottom
Closed
diptorupd opened this issue Oct 8, 2020 · 1 comment · Fixed by #152
Closed

Move _memory submodule directly under dpctl #120

diptorupd opened this issue Oct 8, 2020 · 1 comment · Fixed by #152
Assignees
@PokhodenkoSA
Milestone
gold

Comments

@diptorupd
Copy link
Contributor

We currently need to do import dpctl._memory. Instead we should be able to directly access _memory members by importing dpctl.
@diptorupd diptorupd added this to the gold milestone Oct 8, 2020
@oleksandr-pavlyk oleksandr-pavlyk mentioned this issue Oct 26, 2020
Merged
oleksandr-pavlyk added a commit that referenced this issue Oct 26, 2020
@oleksandr-pavlyk
Implements #120
f3d1899 
1. Removed dpctl.memory
2. Exposed MemoryUSMShared, MemoryUSMDevice, MemoryUSMHost to dpctl
3. When dpctl is cimported MemoryUSMShared, MemoryUSMHost, MemoryUSMDevice
   and Memory classes are exposed.
@oleksandr-pavlyk
Copy link
Contributor

#152 will provide memory containers in dpctl.memory module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PokhodenkoSA PokhodenkoSA

Labels
None yet
Projects
None yet
Milestone
gold
Development

Successfully merging a pull request may close this issue.

Feature/memory zero copy IntelPython/dpctl
3 participants
@PokhodenkoSA @diptorupd @oleksandr-pavlyk