Repository navigation
storagetype-adapted treetransformers
#556
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
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
b1e9083
Make `@cached` usable from other modules
lkdvos 3bc368e
Construct and cache tree transformers per destination storagetype
lkdvos 7b67e65
Recouple complex data with real coefficients in a real gemm on all st…
lkdvos 17484d6
update caching behavior from extension
lkdvos f0bc3c2
simplify CPU versions again - not needed since GPU's have their own
lkdvos 3ee5274
make GPU versions use `@cached`
lkdvos e2022fd
simplify GPU transformers by bypassing some of the Adapt machinery - …
lkdvos 5a3c0c1
avoid additional structure lookups
lkdvos 18bd84c
changes from code review
lkdvos File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Would it make sense to do a similar thing for the "normal" (i.e. CPU) transformers (i.e. simply pass the flat data vector to
add_transform_kernel!and pack the strided subblock information in the transformers)? This would make the workflow a bit more uniform. Currently it is quite complex and confusing to keep track of what is going where along the different codepaths, though I am fine with it for now.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.
I absolutely agree, and had the same thought, although I'll defer this to a follow-up PR to avoid making too many changes at once here. I am somewhat convinced I can actually get both transformer types to align again by making some other changes as well, but to keep things reviewable I'll separate that out.