On Wed, Oct 30, 2019 at 07:26:22AM -0700, Christoph Hellwig wrote: > Looks good, > > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > > Btw, I've been pondering multiple times if we can kill off i_dio_count > again, at least for iomap users. I've added in the request of Thomas > how want to kill non-owner rw_semaphore unlocks. But it turns out those > were needed in other placeѕ and have been added back at least partially. > I'll try to just use those again when I find some time, which should > simplify a lot of the mess we around waiting for direct I/O. I kinda planned to kill off inode_dio_wait() for XFS via range locks. i.e. hold the range lock all the way to DIO completion, then release it there. This allows things like fallocate, truncate, EOF extension, etc to run concurrently with all IO and not require serialisation of the IO in progress to perform extent and size modification operations. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
