-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Support memory pools (introduced in CUDA 11.2) #249
Comments
eyalroz
changed the title
Support memory pools
Support memory pools (introduced in CUDA 11.2)
Apr 16, 2022
So, what would this entail?:
|
Note to self: Remember to add the CUDA-graph-with-memory-node example when implementing this! |
eyalroz
added a commit
that referenced
this issue
Apr 5, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 6, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 6, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 7, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 7, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 7, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 9, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 15, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 16, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
eyalroz
added a commit
that referenced
this issue
Apr 20, 2023
CAVEAT: IPC memopry pool sharing is not well-tested.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CUDA 11.2 introduced a "memory pool" mechanism; we should support it:
Full API documentation here.
The text was updated successfully, but these errors were encountered: