Use Linear Layout to describe 2D block loads #3487
Draft
Conversation
This file contains 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
alexbaden
force-pushed
the
alex/block_loads_layouts
branch
from
c6953ed to
9ea1ff9
Compare
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.
This PR introduces a new linear layout in the Triton Load to LLVM lowering for block loads. The layout describes the block load in terms of three input parameters:
offsetwhich is the 1D offset into the loaded data for a single DPAS invocation inside a sub-groupiterationwhich identifies the DPAS invocation when multiple DPAS invocations share a single loadloadwhich identifies the load index when multiple loads occur for a given operandThe output of the layout function identifies the global
(x,y)tensor coordinate. This was designed to allow composition of the DPAS layout and the load layout to go fromoffset, iteration, loadtoblock, warp, lane, registeror vice versa. Note that I do not encode all the information about the load into the layout currently - I wanted to maintain surjective properties of the layout and it's a bit easier to construct this way. So, sometimes a manual offset must be applied depending on the desired layout parameter.Currently the block load / tile layout is implemented within the existing loop structure. But, the layout was designed to be used to generate the 2D block loads. I left the existing loop structure in-place along with lots of debug info so we can more easily check any regressions. I am planning to remove the existing loop structure and generate loads only using layout parameters in a follow-up PR.
Close #3008