Thanks, any comparison to Drepper is a distinction. I'd like a tool, maybe part of Cachegrind, which said dude, this instruction is thrashing this L2 set. A pr

Thanks, any comparison to Drepper is a distinction. I'd like a tool, maybe part of Cachegrind, which said dude, this instruction is thrashing this L2 set. A profiling virtual machine (Valgrind) is kind of the ultimate lookaside to do this. It could easily (if expensively) evaluate these kinds of queries at each load/store. I think it's better to be able to find these problems than understand them from first principles. I think something like Computer Organization And Design could have a section on cache programming and maybe a problem set. But if I was to revisit this, I'd write something like A Bestiary of Caches which would delineate all of the different caches in a modern CPU. Things like branch prediction target caches, the micro-op cache, the LSD, ... but all in one place.