[GitHub] [tvm] HungYangChang edited a comment on pull request #9751: [Runtime][Pipeline Executor] Add the map logic of global input and subgraph input.

[GitBox <gi...@apache.org>]

HungYangChang edited a comment on pull request #9751:
URL: https://github.com/apache/tvm/pull/9751#issuecomment-1042542646


   Hello @huajsj 
   
   I have questions regarding how to set continuous stream inputs into the pipeline module.
   In your example, there are continuous stream inputs (input1 ~ input4, ...) to feed into the pipeline module.
   
   ![image](https://user-images.githubusercontent.com/70759685/154398420-8d85958f-e28a-459a-a28d-e17d7e9c4a6c.png)
   
   In the[ test_pipeline_executor.py](https://github.com/huajsj/tvm/blob/3ab377d6be2d84fba5f773fb6c7b9e6bf79be184/tests/python/relay/test_pipeline_executor.py#L385), I noticed there is set_input function to set input data.
   ```
   pipeline_module_test.set_input("data_a", data)
   pipeline_module_test.set_input("data_b", data)
   input_data = pipeline_module_test.get_input("data_a")
   tvm.testing.assert_allclose(data, input_data.numpy())
   # Running the pipeline executor in sequential mode.
   pipeline_module_test.run(True)
   ```
   As far as I understand, multiple inputs are essential to utilize the advantage of pipeline executor. 
   However, it seems like it only feeds single input instead of multiple stream inputs.
   I am wondering in your pipeline implementation, do you have any codes to support such multiple stream inputs feeding?
   
   Thanks :)
   


-- 
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: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org