-
Notifications
You must be signed in to change notification settings - Fork 30
Extending dpctl.device_context
with nested contexts
#678
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
Changes from all commits
7f8d3e6
4ad7ae1
21cbea6
50c9dee
438a643
957c5e8
54a023c
087e31f
6ba489e
bfb133f
f964e22
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,6 +61,7 @@ | |
get_current_queue, | ||
get_num_activated_queues, | ||
is_in_device_context, | ||
nested_context_factories, | ||
set_global_queue, | ||
) | ||
|
||
|
@@ -111,6 +112,7 @@ | |
"get_current_queue", | ||
"get_num_activated_queues", | ||
"is_in_device_context", | ||
"nested_context_factories", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not see why this needs to be exposed, especially since I.e. hold then in a dictionary and provide functions to retrieve the list of keys for the registered factories, to add a factory to this list with some key, to remove a factory by its key. Even then, these function would belong to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @PokhodenkoSA If we can avoid adding the function here, let us do it. It just adds more clean up for future. @oleksandr-pavlyk Given that the changes need to make it to 0.12, I am willing to let it slide. Once, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The factory is a key. So we can use list. Also I think we should not guaranty order of contexts.
Partially agree that this is utils. But I think this should be close to
Separate discussion needed: How to make numba redirect context active for compute follows data?
Agree. As they are located close to each other, so clean up will be easy and in the same time. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I think list is simple enough. @oleksandr-pavlyk let me keep things as is. I know that API should be good isolation. But in this case I would like to be simple. |
||
"set_global_queue", | ||
] | ||
__all__ += [ | ||
|
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.
See Keep a Changelog