-
Notifications
You must be signed in to change notification settings - Fork 115
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
RFC to design a unified oneDPL approach to asynchrony #1916
base: main
Are you sure you want to change the base?
Conversation
|
||
### Thrust and CUB | ||
|
||
The Thrust library from Nvidia uses two approaches for its asynchronous algorithms. |
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.
What is more correct : may be NVIDIA ?
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, This reflects our conclusion and reasoning to reject a productized general API, and also describes the context and how we got to that decision.
The proposal aims at designing a consistent approach to asynchronous execution that would be utilized by various APIs of oneDPL, such as asynchronous algorithms and dynamic selection.
Update: the decision was made not to proceed with the proposal, the PR is now for wrapping up and archiving.
The associated discussion: #1917