cfaed Publications

@InProceedings{kusnezoff_ccmcc26,
author = {Alexander Kusnezoff and Jo{\~a}o Paulo Cardoso De Lima and Jeronimo Castrillon and Asif Ali Khan},
booktitle = {Proceedings of the IEEE Cross-disciplinary Conference on Memory-Centric Computing (CCMCC)},
title = {A gem5-based Simulation Framework for Computing-in-{DRAM}},
abstract = {Computing-in-Memory using DRAM (CIMD) has demonstrated substantial energy and throughput gains for memory-bound workloads consisting of bulk-bitwise operations, by performing computation directly within DRAM subarrays. Realizing CIMD, however, requires a redesign of the memory controller and careful mapping of operands onto the memory arrays. Presently, accurate FPGA-based testbeds exist but they are costly and labor-intensive, while open-source simulators are largely trace-based and cannot execute full application runs. The only full-application CIMD simulator available, included with MIMDRAM [1], is built on an outdated version of gem5 and its toolchains. We present gem5-CIMD, a full-system CIMD simulation framework built on the latest gem5 simulation framework. We extend the simulated instruction set from four bitwise operations to sixteen CIM instructions spanning arithmetic, relational, conditional, and utility operations across a range of data types and bitwidths (4 to 64 bits) . A complete memory-management stack – comprising multi-level huge-page support, a CIM-aware allocator, and a subarray-aware address-mapping scheme – ensures that CIM operands are co-located in the same DRAM subarray. In addition, gem5-CIMD is aware of the DRAM refresh interval and faithfully models and schedules the mandatory refresh operations when needed. We provide a CIM standard library intended as a compiler target and evaluate gem5-CIMD on multiple case studies including an end-to-end KNN workload. The simulator sources, including the evaluated workloads, are available at https://github.com/tud-ccc/gem5-CIMD.},
location = {Lyon, France},
publisher = {IEEE},
month = oct,
numpages = {8},
year = {2026},
}