By: Etienne (etienne_lorrain.delete@this.yahoo.fr), December 21, 2017 1:36 am
Room: Moderated Discussions
Travis (travis.downs.delete@this.gmail.com) on December 20, 2017 1:44 pm wrote:
> What feature of the L1L2 path on x86 could cause this?
Maybe it could be that you are writing one single word into an L2 cacheline, so the rest of that cacheline has to be fetched from L3/main memory and that takes time / cannot be completely hidden?
> What feature of the L1L2 path on x86 could cause this?
Maybe it could be that you are writing one single word into an L2 cacheline, so the rest of that cacheline has to be fetched from L3/main memory and that takes time / cannot be completely hidden?