On Fri, Nov 15, 2013 at 10:34:52AM -0500, Trond Myklebust wrote: > > With the current locking model that will require the i_mutex in both > > read and write around the i_dio_count increment. The XFS model avoids > > taking an exclusive lock for the direct I/O fast path. > > > > Is that the xfs_ilock vs xfs_rw_ilock code? xfs_rw_ilock is where you should lock, that are the helpers around the xfs iolock which is the shared/exclusive lock and the i_mutex which we still have to take in the exclusive case as the VFS expects it. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
