JosephTheOctonaut commented on PR #80: URL: https://github.com/apache/tvm-rfcs/pull/80#issuecomment-1164674894
I'm going to write up a few clarifying notes from the chat yesterday; please correct if any of these are wrong. - In `commit_stage(i)` and `wait_stage(i)`, the integer `i` is only used for the commit/wait system. - The integer `i` (as above) is currently considered to be static and constant, but a backend could treat it as a runtime value if necessary. - The current user interface is to write the `"software_pipeline_async_stages"` annotation on a schedule, but there seemed to be support for a sugared version that provides more intuition and visibility in the TIR. - The blocking instruction `wait_stage(i, N)` blocks the main thread / executor (i.e., it cannot be executed by a "worker" thread). This means that the the "queues" (async stages) have their work dispatched to them as they execute, rather that populating a work queue in advance. This seems standard for an "online" host-dispatching-to-coprocessor model. -- 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]
