[ingress][torch] Use Runner in PyTorch backend - #178
Merged
Conversation
Refactors PyTorch MLIR backend to lighthouse's Runner for consistent execution path. Assisted-by: Claude
tkarna
approved these changes
Jun 2, 2026
tkarna
left a comment
tkarna
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
I was thinking we could remove the memory manager if we migrate to use system shared memory for GPU but this PR indicates that having some functionality may be useful in general. Anyway, we can revisit later.
Member
Author
That's an option, for now I follow the existing pattern.
Perhaps, the accepted interface could also be largely simplified. |
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
2 participants
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.
Refactors PyTorch MLIR backend to lighthouse's Runner for consistent execution path.
Assisted-by: Claude