mbs-octoml commented on pull request #9689: URL: https://github.com/apache/tvm/pull/9689#issuecomment-989956646
Hi @xqdan, thx for the comment. That takes us more into memory planning and what @manupa-arm is doing with USMP (including a representation of available memory pools, analysis to determine the conflict set for every abstract buffer, and a realization pass to resolve abstract buffers to physical within a pool). Currently the notion of 'memory/storage scope' we are using here is not connected to the USMP memory pools, or indeed anything at all! It's just a label we push around for use downstream. I see us eventually reconciling the 'flow memory scope constraints' aspect I'm working on here with the 'account for memory scope constraints during scheduling' work, but we'll need to get there gradually. -- 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]
