Btrfs needs to be able to control how data is submitted in the case of fsync to make it a little faster, and really we could get rid of holding the i_mutex altogether as well. So introduce a ->fsync_nolock helper that pushes the responsibility of locking the inode and doing the filemap_write_and_wait_range down into the fs so we can have better control of how we submit the io and do our locking. It looks like ext4 and probably xfs could get away with not taking the i_mutex either, so they may benefit from this as well. Really I could just change ->fsync() to do this and push everything down into all the filesystems, but I wasn't sure how well that would be recieved, so I'm taking this approach. Thanks, Josef -- 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
