Matthew Wilcox 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.
This is an awful lot of work to go thru just to get a glorified ext4 RAMdisk. RAMdisks are one of the worst possible uses for RAM, requiring users to explicitly copy files to them before getting any benefit. Using RAM for a page cache instead brings benefits to all file accesses without requiring any user intervention.
If the NVDIMM range was reserved for exclusive use of the page cache, then you would have an avenue to get persistence/safety for every filesystem mounted on a machine, not just a special case ext4.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
