Skip to content

Conversation

wz337
Copy link
Contributor

@wz337 wz337 commented Jul 30, 2024

Looks like we don't use the name args_sharding anywhere else so just changing it to args_schema for naming consistency

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wconstab @d4l3k @c-p-i-o @tianyu-l @chauhang

Copy link

pytorch-bot bot commented Jul 30, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/132187

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 9bf173b with merge base 3864a2d (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added ciflow/inductor oncall: distributed Add this issue/PR to distributed oncall triage queue labels Jul 30, 2024
@wz337 wz337 added module: dtensor distributed tensor tag topic: not user facing topic category labels Jul 30, 2024
@wz337 wz337 marked this pull request as ready for review July 30, 2024 23:43
@wz337 wz337 requested a review from wanchaol July 30, 2024 23:43

def __str__(self) -> str:
args_sharding: List[str] = []
args_schema: List[str] = []
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason why we don't use args_schema is that it is confliciting with OpSchema.args_schema, so we want to distinguish that, why? args_schema could consists of non Tensor/DTensor arguments, while args_sharding means we only want to include DTensor sharding into the list, excluding non-Tensor/DTensor args

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Follow up question: I thought everything else also get append to args_sharding from here:
https://github.com/pytorch/pytorch/blob/main/torch/distributed/_tensor/_op_schema.py#L289-L290

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm actually you are right, my bad

Copy link
Collaborator

@wanchaol wanchaol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm!

@wz337
Copy link
Contributor Author

wz337 commented Aug 5, 2024

@pytorchmergebot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Aug 5, 2024
@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: dtensor distributed tensor tag oncall: distributed Add this issue/PR to distributed oncall triage queue topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants