Trond Myklebust wrote:
How is this any different than just having your application use mkostemp() to create a temporary dot file, then renaming it when done writing?
That is exactly what it is. There are reasons for implementing it at a lower level in the system, though. Implementing it in glibc: - means applications get it right (today, many don't) - allows for a performance optimization, moving the fsync into a specially spawned off temporary thread, so the main application doesn't stall Implementing it in the kernel allows for some further performance and power optimizations, most notably: - the sync could be turned into an ordering requirement, meaning it can be postponed and even obsoleted by a future version of the file - the ability to postpone the write allows for better power saving -- All rights reversed. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
