-
Notifications
You must be signed in to change notification settings - Fork 25.6k
OpenReg: Support event #140111
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
OpenReg: Support event #140111
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/140111
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 77a8591 with merge base 81d077c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
const noexcept override { | ||
py::gil_scoped_acquire acquire; | ||
get_method("destroyEvent")(event, device_index); | ||
get_method("destroyEvent")((int64_t)event, device_index); |
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.
nit use static_cast<int64_t>(event)
and co
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Support events. Since cpu backend doesn't support asynchronous execution, all event operations will be executed immediately on the executor side. Pull Request resolved: pytorch#140111 Approved by: https://github.com/ezyang
Support events. Since cpu backend doesn't support asynchronous execution, all event operations will be executed immediately on the executor side. Pull Request resolved: pytorch#140111 Approved by: https://github.com/ezyang
Support events. Since cpu backend doesn't support asynchronous execution, all event operations will be executed immediately on the executor side.
cc @ezyang @albanD