Skip to content

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

Merged
merged 30 commits into from
Mar 4, 2025

Conversation

swolchok
Copy link
Contributor

@swolchok swolchok commented Mar 3, 2025

No description provided.

[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@swolchok
Copy link
Contributor Author

swolchok commented Mar 3, 2025

Copy link

pytorch-bot bot commented Mar 3, 2025

🔗 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 Failures

As of commit ddabcf7 with merge base 09ad20a (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 3, 2025
swolchok added a commit that referenced this pull request Mar 3, 2025
ghstack-source-id: f1452c8
ghstack-comment-id: 2695791073
Pull Request resolved: #8902
swolchok added 4 commits March 3, 2025 15:31
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
swolchok added a commit that referenced this pull request Mar 3, 2025
ghstack-source-id: ed24258
ghstack-comment-id: 2695791073
Pull Request resolved: #8902
[ghstack-poisoned]
Copy link
Contributor

@iseeyuan iseeyuan left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

swolchok added 10 commits March 4, 2025 08:11
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
swolchok added a commit that referenced this pull request Mar 4, 2025
ghstack-source-id: 24891e8
ghstack-comment-id: 2695791073
Pull Request resolved: #8902
swolchok added 2 commits March 4, 2025 09:47
[ghstack-poisoned]
[ghstack-poisoned]
swolchok added a commit that referenced this pull request Mar 4, 2025
ghstack-source-id: f3b5256
ghstack-comment-id: 2695791073
Pull Request resolved: #8902
swolchok added 2 commits March 4, 2025 10:00
[ghstack-poisoned]
[ghstack-poisoned]
swolchok added a commit that referenced this pull request Mar 4, 2025
ghstack-source-id: 99c14ff
ghstack-comment-id: 2695791073
Pull Request resolved: #8902
Copy link
Contributor

@mcr229 mcr229 left a 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?

Base automatically changed from gh/swolchok/304/head to main March 4, 2025 19:17
@swolchok
Copy link
Contributor Author

swolchok commented Mar 4, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants