bf2f178f85
This patch adds DRAMSim2 as a memory controller by wrapping the external library and creating a sublass of AbstractMemory that bridges between the semantics of gem5 and the DRAMSim2 interface. The DRAMSim2 wrapper extracts the clock period from the config file. There is no way of extracting this information from DRAMSim2 itself, so we simply read the same config file and get it from there. To properly model the response queue, the wrapper keeps track of how many transactions are in the actual controller, and how many are stacking up waiting to be sent back as responses (in the wrapper). The latter requires us to move away from the queued port and manage the packets ourselves. This is due to DRAMSim2 not having any flow control on the response path. DRAMSim2 assumes that the transactions it is given are matching the burst size of the choosen memory. The wrapper checks to ensure the cache line size of the system matches the burst size of DRAMSim2 as there are currently no provisions to split the system requests. In theory we could allow a cache line size smaller than the burst size, but that would lead to inefficient use of the DRAM, so for not we fatal also in this case.
12 lines
341 B
Plaintext
12 lines
341 B
Plaintext
Follow these steps to get DRAMSim2 as part of gem5
|
|
|
|
1. Download DRAMSim2
|
|
1.1 Go to ext/dramsim2 (this directory)
|
|
1.2 Clone DRAMSim2: git clone git://github.com/dramninjasUMD/DRAMSim2.git
|
|
|
|
2. Compile gem5
|
|
2.1 Business as usual
|
|
|
|
3. Run gem5 with DRAMSim2
|
|
3.1 Use --mem-type=dramsim2 and set the device and system configuration
|