News for hackers. Stuff that matters.
Re:“What the Hardware Does” Is Not What Your Program Does: U... by twic on Sunday July 14, 2019 @06:26PM (#20436614)
The kind of reasoning we do is "if thread A writes to this location, then next time thread B writes to this location, it will have to take ownership of the cache line, which will take N cycles, so let's not do that". I don't think that kind of performance reasoning maps on to anything in Rust.

There are no comments on this comment yet.