Christoph Hellwig wrote:
Another idea, similar to how atime updates work in xfs currently might be interesting: Always update atime in core, but don't start a transaction just for it - instead only flush it when you'd do it anyway, that is another transaction or evicting the inode.
this is sort of having a "dirty" and "dirty atime" split for the inode I suppose.. shouldn't be impossible to do with a bit of vfs support.. - 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