-
Notifications
You must be signed in to change notification settings - Fork 685
Add 1MB temp allocator for executor #13533
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
Add 1MB temp allocator for executor #13533
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13533
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 11 Pending, 2 Unrelated FailuresAs of commit ef81355 with merge base aefdc8d ( NEW FAILURE - The following job has failed:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D80578578 |
This PR needs a
|
56ac74d
to
371472d
Compare
Summary: Method::load creates a PlatformMemoryAllocator as fallback when no temp allocator is provided. So our KernelRuntimeContext will always be PlatformMemoryAllocator since no temp mem is allocated. Overrides et_pal_allocate to allocate code pointer: https://fburl.com/code/216qnnvt Differential Revision: D80578578
This pull request was exported from Phabricator. Differential Revision: D80578578 |
Summary: **Have to ship this as an intermediate step to unblock 3 workstreams on the stack** Modify aten tests to ingress FACTO generated testcases. - Each test gets 30~50 cases with good coverage on - Optimized VS unoptimized flows - dtype switch cases Known issues: - FACTO test class is too big to run on default "heavyweight" CI - current skipping the whole target on CI. Will add back once skycastle flow is ready - some FACTO is creating inputs that kernels does not handle, mainly dtypes - will create exception handling for that. - TODO marks the 2 FACTO doesnt work well on the 2 ops. Reviewed By: manuelcandales, hsharma35 Differential Revision: D79121474
Summary: solve ``` *Error* Unhandled user exception: LoadProhibitedCause (0x00000000) ``` Differential Revision: D80487955
Summary: Method::load creates a PlatformMemoryAllocator as fallback when no temp allocator is provided. So our KernelRuntimeContext will always be PlatformMemoryAllocator since no temp mem is allocated. Overrides et_pal_allocate to allocate code pointer: https://fburl.com/code/216qnnvt Differential Revision: D80578578
371472d
to
3d6b898
Compare
This pull request was exported from Phabricator. Differential Revision: D80578578 |
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.
@zonglinpeng fix merge conflicts
Summary:
Method::load creates a PlatformMemoryAllocator as fallback when no temp allocator is provided. So our KernelRuntimeContext will always be PlatformMemoryAllocator since no temp mem is allocated. Overrides et_pal_allocate to allocate
code pointer: https://fburl.com/code/216qnnvt
Differential Revision: D80578578