On Tue, Nov 21, 2017 at 07:26:06AM +1100, Dave Chinner wrote: > On Mon, Nov 20, 2017 at 08:18:29AM -0800, Matthew Wilcox wrote: > > On Fri, Nov 17, 2017 at 11:39:25AM -0800, Darrick J. Wong wrote: > > > If two programs simultaneously try to write to the same part of a file > > > via direct IO and buffered IO, there's a chance that the post-diowrite > > > pagecache invalidation will fail on the dirty page. When this happens, > > > the dio write succeeded, which means that the page cache is no longer > > > coherent with the disk! > > > > This seems like a good opportunity to talk about what I've been working > > on for solving this problem. The XArray is going to introduce a set > > of entries which can be stored to locations in the page cache that I'm > > calling 'wait entries'. > > What's this XArray thing you speak of? Ah, right, you were on sabbatical at LSFMM this year where I talked about it. Briefly, it's a new API for the radix tree. The data structure is essentially unchanged (minor enhancements), but I'm rationalising existing functionality and adding new abilities. And getting rid of misfeatures like the preload API and implicit GFP flags. My current working tree is here: http://git.infradead.org/users/willy/linux-dax.git/shortlog/refs/heads/xarray-2017-11-20 Ignoring the prep patches, the excitement is all to be found with the commits which start 'xarray:' If you want an example of it in use, I'm pretty happy with this patch that switches the brd driver entirely from the radix tree API to the xarray API: http://git.infradead.org/users/willy/linux-dax.git/commitdiff/dbf96ae943e43563cbbaa26e21b656b6fe8f4b0f I've been pretty liberal with the kernel-doc, but I haven't written out a good .rst file to give an overview of how to use it.
