-
Notifications
You must be signed in to change notification settings - Fork 25.9k
Refactor CUDAAllocatorConfig to reuse AcceleratorAllocatorConfig #150312
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/150312
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (3 Unrelated Failures)As of commit df9befb with merge base bb67660 ( UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
…fig (#150312)" This reverts commit dfacf11. Reverted #150312 on behalf of https://github.com/guangyey due to Static initialization order issue impact the downstream repo ([comment](#150312 (comment)))
|
Starting merge as part of PR stack under #156175 |
3 similar comments
|
Starting merge as part of PR stack under #156175 |
|
Starting merge as part of PR stack under #156175 |
|
Starting merge as part of PR stack under #156175 |
# Motivation As @ScottTodd identified in this [comment](#150312 (comment)), using STL containers like `std::string` and `std::unordered_set` at static init time can cause static initialization order issues. This PR is based on and modified from his original PR: #159607. I’m stacking this PR here to help facilitate the landing and validation process. Co-authored-by: @ScottTodd Pull Request resolved: #159629 Approved by: https://github.com/ScottTodd, https://github.com/albanD
…llocatorConfig instead (#156165) Pull Request resolved: #156165 Approved by: https://github.com/albanD ghstack dependencies: #159629, #150312
# Motivation This PR moves the implementation of `torch.cuda.memory._set_allocator_settings` to `torch._C._accelerator_setAllocatorSettings`. Since the original API was intended as a temporary/internal utility, I am not exposing the new function as a public API. Pull Request resolved: #156175 Approved by: https://github.com/albanD ghstack dependencies: #159629, #150312, #156165
…onfig (pytorch#150312)" Summary: reverting this diff since it caused S551328. Please see D80217492 for dertails. Test Plan: NA Rollback Plan: Differential Revision: D80553588
…onfig (pytorch#150312)" (pytorch#161002) Summary: Pull Request resolved: pytorch#161002 reverting this diff since it caused S551328. Please see D80217492 for dertails. Test Plan: NA Rollback Plan: Reviewed By: sayitmemory, jingsh Differential Revision: D80553588
…onfig (#150312)" (#161002) Summary: reverting this diff since it caused S551328. Please see D80217492 for dertails. Test Plan: NA Rollback Plan: Differential Revision: D80553588 Pull Request resolved: #161002 Approved by: https://github.com/jingsh, https://github.com/izaitsevfb
…locatorConfig (#150312)" (#161002)" This reverts commit a03cc53. Reverted #161002 on behalf of https://github.com/guangyey due to This PR breaks CI TestCudaMallocAsync::test_allocator_settings ([comment](#161002 (comment)))
# Motivation As @ScottTodd identified in this [comment](pytorch#150312 (comment)), using STL containers like `std::string` and `std::unordered_set` at static init time can cause static initialization order issues. This PR is based on and modified from his original PR: pytorch#159607. I’m stacking this PR here to help facilitate the landing and validation process. Co-authored-by: @ScottTodd Pull Request resolved: pytorch#159629 Approved by: https://github.com/ScottTodd, https://github.com/albanD
…orch#150312) # Motivation Refactor `CUDAAllocatorConfig` to reuse `AcceleratorAllocatorConfig` and `ConfigTokenizer`. We would deprecate those option that overleap with `AcceleratorAllocatorConfig` in the following PR and keep them only for BC. Pull Request resolved: pytorch#150312 Approved by: https://github.com/albanD ghstack dependencies: pytorch#159629
…llocatorConfig instead (pytorch#156165) Pull Request resolved: pytorch#156165 Approved by: https://github.com/albanD ghstack dependencies: pytorch#159629, pytorch#150312
…6175) # Motivation This PR moves the implementation of `torch.cuda.memory._set_allocator_settings` to `torch._C._accelerator_setAllocatorSettings`. Since the original API was intended as a tempora 5D99 ry/internal utility, I am not exposing the new function as a public API. Pull Request resolved: pytorch#156175 Approved by: https://github.com/albanD ghstack dependencies: pytorch#159629, pytorch#150312, pytorch#156165
…onfig (pytorch#150312)" (pytorch#161002) Summary: reverting this diff since it caused S551328. Please see D80217492 for dertails. Test Plan: NA Rollback Plan: Differential Revision: D80553588 Pull Request resolved: pytorch#161002 Approved by: https://github.com/jingsh, https://github.com/izaitsevfb
…locatorConfig (pytorch#150312)" (pytorch#161002)" This reverts commit a03cc53. Reverted pytorch#161002 on behalf of https://github.com/guangyey due to This PR breaks CI TestCudaMallocAsync::test_allocator_settings ([comment](pytorch#161002 (comment)))
…fig (pytorch#150312)" (pytorch#161628) This reverts commit ae1a706. Pull Request resolved: pytorch#161628 Approved by: https://github.com/atalman ghstack dependencies: pytorch#161625, pytorch#161626, pytorch#161627
Stack from ghstack (oldest at bottom):
Motivation
Refactor
CUDAAllocatorConfigto reuseAcceleratorAllocatorConfigandConfigTokenizer. We would deprecate those option that overleap withAcceleratorAllocatorConfigin the following PR and keep them only for BC.cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k