adstraw opened a new pull request, #13037:
URL: https://github.com/apache/tvm/pull/13037

   Instead of a single `async_commit_queue_scope` encompassing several 
`async_scope` attributes e.g. as follows:
   
   ```
           with T.attr(0, "async_commit_queue_scope", 0):
               with T.attr(0, "async_scope", 1):
                   for ax0 in T.serial(64):
                       A_global_vtcm_1[ax0] = A[ax0]
               T.attr(0, "async_scope", 1)
               for ax0 in T.serial(64):
                   B_global_vtcm_1[ax0] = B[ax0]
    ```
   
   Force each `async_scope` to be in its own `async_commit_queue_scope` 
attribute e.g. as follows:
   
   ```
           with T.attr(0, "async_commit_queue_scope", 0):
               T.attr(0, "async_scope", 1)
               for ax0 in T.serial(64):
                   A_global_vtcm_1[ax0] = A[ax0]
           with T.attr(0, "async_commit_queue_scope", 0):
               T.attr(0, "async_scope", 1)
               for ax0 in T.serial(64):
                   B_global_vtcm_1[ax0] = B[ax0]
   ```
   
   And adjust "in flight" wait counts accordingly.  In the former case (single 
`async_commit_queue_scope`) the "in flight" wait count is `1` and in the latter 
case (multiple `async_commit_queue_scope`) the "in flight" wait count is `n` 
where `n` is the number of `async_commit_queue_scope` attributes --- `2` in the 
example.
   
   This enables multiple input async DMA using the same queue / stage on 
Hexagon where before it was blocked due to the fact that "in flight" counts are 
managed for each individual DMA with no way to determine if a group of DMAs has 
completed.


-- 
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]

Reply via email to