On Wed, Apr 23, 2014 at 11:20:11PM +0100, Jamie Lokier wrote: > I guess it's also to give the application a way to nudge a preferred > asynchronous writeback order, prior to a synchronous wait. If the > application knows there's a lot of dirty data being generated over > time prior to needing a short fdatasync, it might see it as beneficial > to tell the kernel to start writing that data sooner, so the fdatasync > delay will be shorter. If they want to do an async writeback pass first they can just use sync_file_range for it, that's the only thing it's actually useful for. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
