random thought: sync() / fsync() / fdatasync() are like execution-serializing barriers. a lighter barrier type might be useful for things like package managers: only guarantee that all future writes happen after all previous ones, maybe with an option for specifying constraints
-
-
the reason fsync and friends are expensive is that the cache flush goes to the disk.... without the disk cache being part of the serialization the OS cannot provide any actual ordering guarantees. "All Storage is a Lie " - Andre Hedrick
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.