Hi Everyone,
I recently started experimenting with a new x86 user space (based on
Debian Wheezy) and ran into a problem with the decode cache. It seems
like the boot process (probably udev) is starting a lot of small
processes, which causes the decode cache size to explode since it stores
every single static instruction that the decoder encounters. On my
system, I ended up using more than 8 GiB of memory long before the the
boot process completed.
My current solution is to set an upper limit on the decode cache size
and when that is reached, I randomly remove half of the entries. In
practice, it might be better to completely flush the cache since that
keeps the code a bit simpler.
Does anyone have any opinions about this? Gabe?
I'll push my proposed fix to my fixes branch [1] on GitHub later today
if anyone wants to have a look.
//Andreas
[1] https://github.com/andysan/gem5/tree/fixes
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
