Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AXIToTL component can‘t support axi outstanding? #3715

Open
AD738560581 opened this issue Feb 7, 2025 · 0 comments
Open

AXIToTL component can‘t support axi outstanding? #3715

AD738560581 opened this issue Feb 7, 2025 · 0 comments

Comments

@AD738560581
Copy link

Hello @terpstra @aswaterman , we conducted secondary development based on Rocket and developed a coprocessor that supports the RVV instruction set. We will convert AXI interface to Tile link interface by AXIToTL component, because its external memory access interface is AXI4 interface.
However,we found that if an outstanding transmission is initiated (multiple consecutive ar commands with the same ID), AXIToTL will only issue one tilelink read request until the data is returned, and then issue the next tilelink read request, which will seriously affect the memory access performance of RVV.
How can I fix this performance point? Have you encountered similar problems before?I tried to modify the FIFO type of TLFIFOFixer module and found that allFIFO and allVolatile types can issue multiple tilelink commands, but there will be an assertion failure which is "channel re-used a source ID(connected at myrocc.scala)".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant