>So, semantics of ->sync_page() are roughly "kick underlying storage >driver to actually perform all IO queued for this page, and, maybe, for >other pages on this device too".
I prefer to think of it in a more modular sense. To preserve modularity, the caller of sync_page() can't know anything about I/O scheduling. So I think the semantics of ->sync_page() are "Someone is about to wait for the results of the previously requested write_page on this page." It's completely up to the owner of the address space to figure out what would be appropriate to do given that information. I agree that for the conventional filesystem and device types for which this interface was designed, the appropriate response would be to start any queued I/O. -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
