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

perf: lane vrf-alu-vrf operations not pipelined #223

Open
SharzyL opened this issue May 1, 2023 · 0 comments
Open

perf: lane vrf-alu-vrf operations not pipelined #223

SharzyL opened this issue May 1, 2023 · 0 comments

Comments

@SharzyL
Copy link
Contributor

SharzyL commented May 1, 2023

From the following waveform (from mill -i tests.run[stripmining-huge.mlir]), it can be observed that when executing vadd.vi v8, v8, 2, vrf write is triggered one time per 5 cycles, which means it only utilized 1/5 bandwidth of vrf and alu. 5 cycles consists of

  1. read vrf
  2. vrf output
  3. save vrf output to reg
  4. compute and save result
  5. write vrf

They should be pipelined to avoid wasting bandwidth.

image

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