[TIR][Schedule] Support for specific consumer block targeting in cache_write #13510
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.
Hi, this change try add optional
consumer_blocks
param tocache_write
symmetrically, following change oncache_read
of #12505.This is helpful when there are multiple consumers to the targeting block who also write to global output, and when we do
cache_write
, we may want to control some of the consumers read data reside on cache.As a comparation, for
s.cache_read(B, 0, "cache_scope", consumer_blocks=[B])
:For
s.cache_write(P, 0, "cache_scope", consumer_blocks=[B])
cc @Hzfengsy @jwfromm