Describe the bug
It seems that DMASpeed and DMAWidth don't limit SSD bandwidth.
To Reproduce
Steps to reproduce the behavior:
Modify sample.cfg in SimpleSSD-Standalone to avoid OS I/O stack being the bottleneck.
-blocksize = 4K
+blocksize = 128K
Modify sample.cfg in simplessd to avoid SSD DRAM being the bottleneck:
## DRAM structure parameters
-Channel = 1
+Channel = 4
Rank = 1
Bank = 8
Chip = 1
Please notice that this is SSD DRAM #channels, not SSD flash #channels.
Expected behavior
The performance should be limited by NVDDR transfers which is
DMASpeed * DMAWidth / 8 * #channels_in_SSD = 0.4 G/s * 1B * 8 = 3.2 GB/s
But the simulation results suggest the achieved SSD throughput is 11.14 GB/s.
I suspect it is related to how conflicts are resolved in PAL2.cc.
But I couldn't fully grasp the logic there.
Describe the bug
It seems that DMASpeed and DMAWidth don't limit SSD bandwidth.
To Reproduce
Steps to reproduce the behavior:
Modify sample.cfg in SimpleSSD-Standalone to avoid OS I/O stack being the bottleneck.
Modify sample.cfg in simplessd to avoid SSD DRAM being the bottleneck:
Please notice that this is SSD DRAM #channels, not SSD flash #channels.
Expected behavior
The performance should be limited by NVDDR transfers which is
DMASpeed * DMAWidth / 8 * #channels_in_SSD = 0.4 G/s * 1B * 8 = 3.2 GB/sBut the simulation results suggest the achieved SSD throughput is 11.14 GB/s.
I suspect it is related to how
conflictsare resolved in PAL2.cc.But I couldn't fully grasp the logic there.