-
Notifications
You must be signed in to change notification settings - Fork 113
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
Clarify Acquire/Release behavior for external memory #1176
Conversation
Looks good generally. |
api/opencl_runtime_layer.asciidoc
Outdated
that was one of the devices specified via {CL_MEM_DEVICE_HANDLE_LIST_KHR} | ||
when the memory object was imported using {clCreateBufferWithProperties} or | ||
{clCreateImageWithProperties}. If {CL_MEM_DEVICE_HANDLE_LIST_KHR} was not | ||
specified, the acquire can be performed on a command-queue associated with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release can be performed on a command queue ...
Address some of the comments that were left out in earlier update.
The following restrictions shall apply - | ||
* Each memory object must be released only once. Releasing a memory object | ||
multiple times without acquiring it results in implementation-defined | ||
behavior. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strictly speaking this is ambiguous (and so is the mirror statement above for acquire operations). There might be a better formulation, possibly describing this in terms of number of acquire/release operations but the current text is a clear step forward so fine if you want to merge it as is.
Fix the typo suggested by Kevin to replace aquired to acquired. Co-authored-by: Kévin Petit <kevin.petit@arm.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging as discussed in the July 16th memory subgroup.
Clarify Acquire/Release behavior for external memory specs to call out the scope of operations as well as
the behavior in case of multiple acquire/release calls.
Fixes #1078, #1086