Last I remember (which, it has been a while), on x86 and friends anyway, ~all reads go to cache. So the request is somewhat nonsensical I believe? You might th

Last I remember (which, it has been a while), on x86 and friends anyway, ~all reads go to cache. So the request is somewhat nonsensical I believe? You might then ask how to keep it there, but I doubt you can. Your best bet is to keep the working set of used memory small during the steps you care about. Also could be worth keeping in mind that caches work on "lines", small blocks of data. So you can give yourself a small edge if you keep all the crap you're going to use in one contiguous block of memory.