On Tue, Jul 12, 2016 at 12:42:28PM +0300, Ilya Lantukh wrote: > Hi all, > > We are considering to use libaio in our project as an optional > alternative to Java NIO. Our goal is to improve performance while > maintaining durability. > > We have performed tests on different storage devices. Files were > opened with flags: O_WRONLY | O_DIRECT | O_DSYNC. However, on some SSD > devices O_DSYNC causes io_submit() to block until operation is > finished, which is not acceptable in our case. What is your exact setup? Sounds like you're using a file system and not a block device node. Which filesystem shows this behavior? > > The question is: do libaio writes with only WRONLY | O_DIRECT flags > provide any durability guarantees? No, they don't, you need O_DSYNC for that. -- 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
