SparrowOS is always identity mapped

http://mechanical-sympathy.blogspot.com/2013/02/cpu-cache-flushing-fallacy.html

comments, HES STILL ALIIIVE

I didn't understand his comment... the post was not about memory pagefaults, how does his comment make sense?

>>2
i dont understand his comment either

god knows how that guy can operate a compiler

>>2
The article: "Caches never flush you fools! <20 paragraphs later> … except well of course they do."
The comment: "SparrowOS avoids that by never changing the memory map."

>>4
Only the option of memory mapping or a direct translation don't really has an impact on cache miss%, of course it will have a little less predictable spatial locality but still that's not what the blog post addressed, no pun intended. No mention of any pagination scheme on there.

x86 caches are like toilets. If you don't flush them they fill up with shitty x86 code.