-
Notifications
You must be signed in to change notification settings - Fork 526
Add cpu_thread setting logic to xnn_executor_runner #8902
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
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8902
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit ddabcf7 with merge base 09ad20a ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
LGTM. Thanks!
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.
this seems fine, but honestly coming back to this after year+ since our first release, do we need to have an xnn_executor_runner which is separate from the executor_runner? Should our CMake just be if BUILD_XNNPACK=ON, we link XNNPACK to executor_runner, if not then we dont?
sounds like a great idea to me! this change is still an incremental improvement though so I will land it. On another note, CI is green, rebasing to make sure extra changes from previous commit go away and then merging without waiting for CI to run again |
No description provided.