Add urUSMPoolFree function to spec #767
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To free previously allocated USM memory urUSMFree accepts a context handle and pointer. If it's memory from a pool we need to identify the pool from which the memory was allocated. We can avoid this overhead by having a function that accepts pool handle.
kswiecicki
force-pushed
the
usm-pool-free
branch
from
d268e70
to
0146db5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To free previously allocated USM memory urUSMFree accepts a context handle and pointer. If it's memory from a pool we need to identify the pool from which the memory was allocated. We can avoid this overhead by having a function that accepts pool handle.