-
Notifications
You must be signed in to change notification settings - Fork 685
Updating documentation for cmake dtype selective build #12112
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12112
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit e9745f4 with merge base adb5318 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "release notes: none" |
cc @psiddh |
|
||
### Select ops from model | ||
|
||
This API lets users pass in a pte file of an exported model. When used, the pte file will be parsed to generate a yaml file that enumerates the operators and dtypes used in the model. |
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.
Is the fact that a yaml file is generated relevant to the end user? The above documentation makes it seem like the model yaml is not a user facing construct, only the pte, or the root ops list are exposed methods of passing selective information.
Also in general I would say "root" ops is misleading since ET doesnt have transitive ops. We should just call it the op list.
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.
When using the model API, the generated YAML can be as an input to the selective build process, like when using the yaml API directly. The difference being that a user doesn't have to manually craft a yaml, but can pass in a pte.
I agree, root ops is not a great name, but it seems to be used in other places as well, e.g. https://github.com/BujSet/executorch/blob/main/codegen/tools/gen_oplist.py#L234-L243. For consistency, I think we should keep it as root ops, and a separate PR should refactor this to something more meaningful, what do you think?
a6f2443
to
8da8a29
Compare
8da8a29
to
e9745f4
Compare
@lucylq @BujSet @larryliu0820 should this part of the cherry-pick for 0.7? |
Yes, I think we can include it as all the code changes are there. @BujSet could you cherry-pick it following the instructions in #11075 ? |
@pytorchbot cherry-pick --onto release/0.7 -c docs |
### Summary Updating documentation for cmake dtype selective build with model API. Table at `selective_build_model_doc/docs/source/kernel-library-selective-build.md` now looks like:  Fixes #12065 cc @mergennachin @byjlw (cherry picked from commit f673a4b)
Cherry picking #12112The cherry pick PR is at #12123 The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
Updating documentation for cmake dtype selective build with model API. Table at `selective_build_model_doc/docs/source/kernel-library-selective-build.md` now looks like:  Fixes pytorch#12065 cc @mergennachin @byjlw
Summary
Updating documentation for cmake dtype selective build with model API. Table at
selective_build_model_doc/docs/source/kernel-library-selective-build.md
now looks like:Fixes #12065
cc @mergennachin @byjlw