For the record, I tried out a custom allocator for requests. I measured how long it took to run twolf smred on ARM/gem5.opt with no modification, with a custom allocator that keeps around all deleted requests for reuse, and one that only kept around one. I was not able to measure any consistent improvement in performance with the custom allocator.
Gabe On Thu, Nov 29, 2018 at 5:41 PM Gabe Black <gabebl...@google.com> wrote: > As a side note, tcmalloc has bitten me a number of times here. I've run >> valgind with tcmalloc and seen "0 bytes allocated and 0 bytes deleted" >> after waiting for hours too many times. I have finally learned to >> recompile >> everything using "--without-tcmalloc" before running valgind. >> >> > Yeah, I was thinking before the way to set everything up for valgrind is a > little too non-obvious. It would be nice to have some small scripts or > something to help set that up. > > Gabe > _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
