"Ma, Jianpeng" <jianpeng.ma@xxxxxxxxx> writes: > For aio+directio: > After io_submit, the content in request-queue of block-device. Maybe. It might be in the per-cpu plug list, or in the elevator's queues. > In blkdev_fsync(), it will cal blkdev_issue_flush. This operation make > all request to disk. blkdev_issue_flush send a FLUSH to the device. It does nothing to re-order existing requests in the queue. Thus, as Zach said, if you want to ensure data is on stable media, then you should wait for the I/O to complete and then issue the fsync. Cheers, Jeff -- 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
