-
Notifications
You must be signed in to change notification settings - Fork 14k
cuda: optimize SOLVE_TRI using registers and FMAF #17703
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
Open
wsbagnsv1
wants to merge
13
commits into
ggml-org:master
Choose a base branch
from
wsbagnsv1:TRI_SOLVE
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+28
−36
Open
Changes from 6 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
9e39850
ggml-cuda: optimize solve_tri_f32_fast and fix stride handling
wsbagnsv1 4c9c634
Merge branch 'ggml-org:master' into TRI_SOLVE
wsbagnsv1 b14882f
Small cleanup
wsbagnsv1 68881ef
Remove comments in solve_tri.cu
wsbagnsv1 a29836b
Merge branch 'ggml-org:master' into TRI_SOLVE
wsbagnsv1 642e898
Merge branch 'ggml-org:master' into TRI_SOLVE
wsbagnsv1 c55b5bf
Update ggml/src/ggml-cuda/solve_tri.cu
wsbagnsv1 2fd9264
Update ggml/src/ggml-cuda/solve_tri.cu
wsbagnsv1 b27ce89
Update ggml/src/ggml-cuda/solve_tri.cu
wsbagnsv1 12d108a
Merge branch 'ggml-org:master' into TRI_SOLVE
wsbagnsv1 ec9b6f9
Use const for variables in solve_tri.cu
wsbagnsv1 a34a45a
Replace fmaf with more readable code
wsbagnsv1 4a63709
remove last fmaf
wsbagnsv1 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
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.
Please use const wherever applicable so that one can easily tell which variables are subject to change in the future.
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.
Both of those are changed in the #pragma unroll loops so they cant be const (;
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.
Seems like you're right. And confusion like this is precisely why I want a clear and consistent distinction between const and non-const vatiables.
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.
Should i add a comment to clear things up?
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.
A comment explaining the purposes of
x_lowandx_highwould be nice to have but not required. The problem here was rather that I read the kernel top to bottom, wasn't sure whether these particular values are supposed to be constant, didn't see the part further down where they are modified (but saw that you are not consistently adding const where applicable), and then left this comment.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.
Ive added const to every variable that should use it now (;