-
Notifications
You must be signed in to change notification settings - Fork 124
[UR] Initial spec for the enqueue allocation API #2295
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
Conversation
af9b768 to
d0c58ef
Compare
d0c58ef to
697d6f7
Compare
2ba7bc6 to
bc9d8a4
Compare
bc9d8a4 to
c854119
Compare
|
@oneapi-src/unified-runtime-native-cpu-write, @oneapi-src/unified-runtime-opencl-write, @oneapi-src/unified-runtime-hip-write, @oneapi-src/unified-runtime-cuda-write, @oneapi-src/unified-runtime-level-zero-write. |
aarongreig
left a comment
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.
LGTM, just a couple of typos
scripts/core/EXP-ASYNC-ALLOC.rst
Outdated
| UR command enqueues without forcing synchronization points in the asynchronous | ||
| command DAG associated with a queue. This can allow applications to compose | ||
| memory allocation and command execution asynchronously, which can improve | ||
| performancet. |
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.
| performancet. | |
| performance. |
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.
Thanks, I've fixed the typos.
scripts/core/exp-async-alloc.yml
Outdated
| name: hQueue | ||
| desc: "[in] handle of the queue object" | ||
| - type: $x_usm_pool_handle_t | ||
| desc: "[in][optional] handle of the USM memory pooliptor" |
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.
| desc: "[in][optional] handle of the USM memory pooliptor" | |
| desc: "[in][optional] handle of the USM memory pool" |
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.
Done.
c854119 to
6bb6057
Compare
6bb6057 to
6d85083
Compare
6d85083 to
9dfaf6a
Compare
|
These spec changes taken from this PR are still in flight and up for discussion. Further spec changes may be necessary. I would suggest holding off merging this PR until the spec is finalized. |
9dfaf6a to
3563ff2
Compare
3563ff2 to
609c7fe
Compare
15968d5 to
562ef3e
Compare
562ef3e to
074d209
Compare
First basic work in progress spec.
074d209 to
9317705
Compare
Unified Runtime -> intel/llvm Repo Move NoticeInformationThe source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory, The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime. The contribution guide has been updated with new instructions for contributing to Unified Runtime. PR MigrationAll open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days. Should you wish to continue with your PR you will need to migrate it to intel/llvm. This is an automated comment. |
Unified Runtime -> intel/llvm Repo Move NoticeFollowing on from the previous notice, we have now enabled workflows to automatically label and close PRs because the Unified Runtime source code has moved to intel/llvm. This PR has now been marked with the Please review the previous notice for more information, including assistance with migrating your PR to intel/llvm. Should there be a reason for this PR to remain open, manually remove the This is an automated comment. |
Automatic PR Closure NoticeInformationThis PR has been closed automatically. It was marked with the All Unified Runtime development should be done in intel/llvm, details can be found in the updated contribution guide. Next StepsShould you wish to re-open this PR it must be moved to intel/llvm. We have provided a script to help automate this process, otherwise no actions are required. This is an automated comment. |
Those changes are based on the initial PR (#2180) with minor changes, wording and CI testing fixes.