rename ought to imply a barrier because there are no useful cases for a non-barrier rename, and plenty of cases for a
rename-with-barrier. Forcing application authors to use a separate call will simply allow them to forget it, and will ensure that existing applications are still unsafe. A barrier-on-
rename scheme adds safety with no loss in expressiveness, and is a performance increase over
fsync, which is, well, synchronous.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds