#prefetch — Public Fediverse posts

@m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

@m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

@m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

@m20k #inorder+#prefetch is fantastic for energy efficiency, but #OoO’s flexibility in the face of cache misses and #branchmissprediction leads to much better performance for many workloads. By “scaling” I meant scaling to higher performance with wider issue, requiring even better BP accuracy and covering for even longer #cachemiss penalties.

We can do better than scaling this instruction-at-a-time model we have been using since the 1950es, but that’s for another toot.

Re-sharing a 2019 article from @dfir that I just became aware of from @[email protected] -->

Running an executable in an #AlternateDataStream ( #ADS on #NTFS ) resulted in a #prefetch file that is also in an ADS. At that time, parsing tools seemed to miss this prefetch file due to it being in an ADS. #DFIR #windows https://www.binary-zone.com/2019/05/26/creating-a-hidden-prefetch-file-to-bypass-normal-forensic-analysis/

This is interesting behavior. Has anyone observed this in the wild?

Re-sharing a 2019 article from @dfir that I just became aware of from @[email protected] -->

Running an executable in an #AlternateDataStream ( #ADS on #NTFS ) resulted in a #prefetch file that is also in an ADS. At that time, parsing tools seemed to miss this prefetch file due to it being in an ADS. #DFIR #windows https://www.binary-zone.com/2019/05/26/creating-a-hidden-prefetch-file-to-bypass-normal-forensic-analysis/

This is interesting behavior. Has anyone observed this in the wild?