yzh119 commented on PR #14161: URL: https://github.com/apache/tvm/pull/14161#issuecomment-1451958988
Hi @quic-sanirudh yes you are correct, such cases would occur when there are multiple consumer blocks, and we should suggest users using `cache_read`/`cache_write` in these cases, which analyzes the union of access regions of all consumer blocks. Supporting this feature for `reindex_cache_read_write` would make things complicated, for example, in your program you tried to reindex cache read buffer `A` in block `B`, it's inevitable that we need to change the indices of buffer `A` in block `C` as well which is not desired. Considering that most of the use cases of `reindex_cache_read` are orchestrating data movement from shared memory to local registers and do not involve multiple consumer blocks, I suggest: 1. only support single consumer block 2. remove the `consumer_blocks` argument in API 3. emphasize this point in docstring and suggest user to use `cache_read`/`cache_write` in this case. Do you think this acceptable? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
