On Thu, Dec 05, 2013 at 01:02:46PM -0700, Ross Zwisler wrote: > This is a port of the XIP functionality found in the current version of > ext2. This patch set is intended to achieve feature parity with XIP in > ext2 rather than non-XIP in ext4. In particular, it lacks support for > splice and AIO. We'll be submitting patches in the future to add that > functionality, but we think this is a good start. > > The motivation behind this work is that we believe that the XIP feature > will begin to find new uses as various persistent memory devices and > technologies come on to the market. Having direct, byte-addressable > access to persistent memory without having an additional copy in the > page cache can be a win in terms of I/O latency and overall memory > usage. > > This patch applies cleanly to v3.13-rc2, and was tested using brd as our > block driver. I think I see a significant problem here with XIP write support: unwritten extents. xip_file_write() has no concept of post IO completion processing - it assumes that all that is necessary is to memcpy() the data into the backing memory obtained by ->get_xip_mem(), and that's all it needs to do. For ext4 (and other filesystems that use unwritten extents) they need a callback - normally done from bio completion - to run transactions to convert extent status from unwritten to written, or run other post-IO completion operations. I don't see any hooks into ext4 to turn off preallocation (e.g. fallocate is explicitly hooked up for XIP) when XIP is in use, so I can't see how XIP can work with such filesystem requirements without further infrastructure being added. i.e. bypassing the need for the page cache does not remove the need to post-IO completion notification to the filesystem.... Indeed, for making filesystems like XFS be able to use XIP, we're going to need such facilities to be provided by the XIP infrastructure.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
