You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @alanvgreen and @tcal-x , I would appreciate it if you could clarify a simple question I need to be answered soon, since I have a deadline:
What is the use of the L2 cache in the CFU framework especially on FPGA setups, since as I understand it is inherently the same memory structure as L1 in the device level - ie, single cycle BRAM units. So, does it make sense to have an L2 in the hierarchy or is there some inherently different memory arch. used that consumes lesser resources for L2 per byte.
Thanks,
Bala.
The text was updated successfully, but these errors were encountered:
Hi @bala122 , this question is more about the LiteX SoC architecture, so it might be worth asking on the #litex IRC channel (or find them on discord as well these days).
But I can take a guess --- even with the same building blocks, the BRAMs can be organized differently. I expect that the L2 cache can transfer wide data lines to/from the SDRAM with multiple BRAMs in parallel, and then connect to the 32b Wishbone bus. The Wishbone system bus is between the L2 cache and the VexRiscv's L1 caches. The L1 caches are tightly integrated with the VexRiscv's pipeline. So they each serve specific purposes; eliminating either the L1 or L2 cache and putting all of its resources to the other side would likely hurt performance.
Hi @alanvgreen and @tcal-x ,
I would appreciate it if you could clarify a simple question I need to be answered soon, since I have a deadline:
What is the use of the L2 cache in the CFU framework especially on FPGA setups, since as I understand it is inherently the same memory structure as L1 in the device level - ie, single cycle BRAM units. So, does it make sense to have an L2 in the hierarchy or is there some inherently different memory arch. used that consumes lesser resources for L2 per byte.
Thanks,
Bala.
The text was updated successfully, but these errors were encountered: