On 4/5/06, Progga <abulfazl@xxxxxxxxx> wrote: > On Wed, Apr 05, 2006 at 05:02:20AM +0100, Glynn Clements wrote: > > > The O_DIRECT flag suggested by Steve is probably overkill. It requires > > that the buffer start address, buffer size and file offset are all > > multiples of the filesystem's block size, and only works on some > > filesystems. > > Although it works for a single file, how good is fsync() in this case? fsync(2) does not ensure that all data has actually been written to disk. The controller may indicate that all data is stable, but it does so even if it is still in its internal cache. From this point of view, fsync(2) is not a replacement for O_DIRECT. \Steve - : send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
