[AutoWS] Support multi-buffering TMEM accumulators with leftover memory#1026
Open
njriasan wants to merge 6 commits intofacebookexperimental:mainfrom
Open
[AutoWS] Support multi-buffering TMEM accumulators with leftover memory#1026njriasan wants to merge 6 commits intofacebookexperimental:mainfrom
njriasan wants to merge 6 commits intofacebookexperimental:mainfrom
Conversation
njriasan
commented
Mar 3, 2026
| // (AsyncCLCTryCancelOp) once CLC support lands in pure Triton. | ||
| bool isLikelyPersistentKernel() { | ||
| bool found = false; | ||
| operation->walk([&](tt::GetNumProgramsOp) { found = true; }); |
Contributor
Author
There was a problem hiding this comment.
Claude generated this heuristic. Honestly this is fairly consistent with my kernel authoring experience.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for multi-buffering TMEM allocations based on leftover memory in the MemoryPlanner. This includes two high-level changes:
I don't have explicit testing numbers because this was part of a broader set of changes that got our perf.