For one you make ->aio_read/write trivial wrappers around ->read_iter and ->write_iter. Instead of keeping this duplication around please make sure to entirely kill ->aio_read/write and always use your new methods. Without that we'll get into a complete mess like the old ->aio_read/write vs ->readv/writev again. A similar thing applies to the ->direct_IO/direct_IO_bvec interface -
Yeah, that's reasonable. Perhaps obviously, we started with new entry points to minimize the amount of churn we'd have to go through to test the change in behaviour. It's going to be messy to try and abstract away the pinning and dirtying of the iter regions from direct IO through the iter interface, but maybe not horribly so. - z -- 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
