* Jamie Lokier (jamie@xxxxxxxxxxxxx) wrote: > Abhijit Paithankar wrote: > > One way to do it is to fsync every few operations. However, fsync is > > blocking and affects performance. > > > > The other (more efficient) way is to have the filesystem notify the > > application when a transaction/change is written to disk. > > Is this more efficient than aio_fsync, and if so, why? > > For file writes, aio_fsync seems like a cleaner interface, and if > that's not fast enough, it could be made faster - perhaps using code > form this patch. (An aio_fsync_ranges would be even better). > > -- Jamie Hi, aio_fsync does not provide any relationship between the metadata operations and journal commit. There is no mechanism to track operations which made it to the journal and the ones that did not. With the journal notifications patch we will be able to know exactly which metadata change hit the journal and when. Thanks! Abhijit -- 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
