Tilize with val padding results in L1 cache OOM #16633
Open
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.
Ticket
Link to Github Issue #15950
Problem description
In the current implementation of multi-core tilize with val padding, the parallelization is only over the columns, meaning the whole row is being passed to the same core. This causes L1 OOM when the tensor has a large width
What's changed
In multi-core tilize, we are calculating the maximum available L1 and the estimated cb size. We are running the single core implementation if there isn't enough space. The multi-core implementation will be improved in the future to cover row and column parallelization
Checklist