Steve Graegert 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. If the drive doesn't accurately indicate whether data has been written to the physical medium, that will affect everything, including O_DIRECT. There have been cases of drives which indicate that data has been written even when it's still in the cache, in order to improve benchmark scores. I don't believe that there's any difference between O_SYNC, O_DIRECT or fsync() in terms of their interpretation of "written to the hardware"; they all send a "flush" command to the drive and block until the drive reports completion. The advantage of O_DIRECT is that it won't displace existing blocks from the kernel's buffer cache, which might be useful if you're writing a lot of data and won't be reading it back in any time soon. According to: http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B99794 that is more than what FILE_FLAG_WRITE_THROUGH does: The FILE_FLAG_WRITE_THROUGH flag for CreateFile() causes any writes made to that handle to be written directly to the file without being buffered. The data is cached (stored in the disk cache); however, it is still written directly to the file. This method allows a read operation on that data to satisfy the read request from cached data (if it's still there), rather than having to do a file read to get the data. The write call doesn't return until the data is written to the file. This applies to remote writes as well--the network redirector passes the FILE_FLAG_WRITE_THROUGH flag to the server so that the server knows not to satisfy the write request until the data is written to the file. O_DIRECT appears closer to FILE_FLAG_NO_BUFFERING: The FILE_FLAG_NO_BUFFERING takes this concept one step further and eliminates all read-ahead file buffering and disk caching as well, so that all reads are guaranteed to come from the file and not from any system buffer or disk cache. When using FILE_FLAG_NO_BUFFERING, disk reads and writes must be done on sector boundaries, and buffer addresses must be aligned on disk sector boundaries in memory. IOW, FILE_FLAG_WRITE_THROUGH corresponds to O_SYNC while FILE_FLAG_NO_BUFFERING corresponds to O_DIRECT. -- Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx> - : 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
