-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[DTensor] Returned new placements for neg dim in global info #113922
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
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/113922
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 68244cc with merge base 6ed20af ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
[ghstack-poisoned]
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.
My feeling is that since we normalized the shard dim for every public API, from_local, distribute_tensor and redistribute, we don't need to do normalize again when computing the global info? maybe we can simply delete this normalization logic
…ith assert in helper" This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected. [ghstack-poisoned]
…lper" This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected. [ghstack-poisoned]
This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected. Pull Request resolved: #114141 Approved by: https://github.com/wanchaol ghstack dependencies: #113919, #113924, #114134, #113925, #113930
Stack from ghstack (oldest at bottom):
DTensorSpec#113915distribute_tensor#113930grad_placementswas tuple #113925redistribute#113924_Partial,Replicatefrozen dataclasses #113919shard_spec->placementsin test file #113917op_callin no-mesh dispatch assert message #113903_get_registryreturnNoneif no APIs applied #113654