-
|
Hello, In the A100 configs, the row/bank/channel/column bit allocations correspond to only a few hundred MB to a few GB of modeled DRAM capacity. (228)/(10243) = 0.25 * 40 (n_mem) = 10 GB Is the scaled-down DRAM capacity intentional for simulation performance reasons? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
dram capacity is not modeled. CPU-GPU transfer is not modeled, thus there is no point in modeling dram capacity. Everything is assumed to be within dram when a kernel starts, which is typical of how you would launch a kernel. That being said, the dram model does not accurately represent contemporary HBMs. It's still modeling HBM1, and we scale the number of channels to match HBM3 BW. Right now, there is nothing we can release as an accurate contemporary HBM3. |
Beta Was this translation helpful? Give feedback.
dram capacity is not modeled. CPU-GPU transfer is not modeled, thus there is no point in modeling dram capacity. Everything is assumed to be within dram when a kernel starts, which is typical of how you would launch a kernel.
That being said, the dram model does not accurately represent contemporary HBMs. It's still modeling HBM1, and we scale the number of channels to match HBM3 BW. Right now, there is nothing we can release as an accurate contemporary HBM3.
There are other projects that integrate gpgpu-sim and more accurate DRAM models, such as Ramulator. With some hacks, it should be easily adapted to Accel-Sim.