-
Notifications
You must be signed in to change notification settings - Fork 17
[Transform] Accelerate Utilities #328
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
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
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.
I'm assuming force
name means that takes precedent over any other context, e.g. force_cpu_offload
overrules disable_offload
, and the module/tensor will be moved to CPU?
Signed-off-by: Kyle Sayers <[email protected]>
@brian-dellabetta Not necessarily. I use the word "force" because This method "forces" the tensors to go onto the meta device by nature of specifying a very granular device map (dispatch_model is a weird method :/ ) |
Signed-off-by: Kyle Sayers <[email protected]>
Purpose
Changes
register_offload_module
delete_offload_module
force_cpu_offload
disable_offload
andalign_modules
Testing
register_offload_module
,delete_offload_module
, andforce_cpu_offload