On Tue, 26 Aug 2014 23:45:20 -0400 Matthew Wilcox <matthew.r.wilcox@xxxxxxxxx> wrote: > One of the primary uses for NV-DIMMs is to expose them as a block device > and use a filesystem to store files on the NV-DIMM. While that works, > it currently wastes memory and CPU time buffering the files in the page > cache. We have support in ext2 for bypassing the page cache, but it > has some races which are unfixable in the current design. This series > of patches rewrite the underlying support, and add support for direct > access to ext4. Sat down to read all this but I'm finding it rather unwieldy - it's just a great blob of code. Is there some overall what-it-does-and-how-it-does-it roadmap? Some explanation of why one would use ext4 instead of, say, suitably-modified ramfs/tmpfs/rd/etc? Performance testing results? Carsten Otte wrote filemap_xip.c and may be a useful reviewer of this work. All the patch subjects violate Documentation/SubmittingPatches section 15 ;) -- 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
