On Wed, 27 Aug 2014, Andrew Morton wrote: > 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? Matthew gave a talk about DAX at the kernel summit. Its a great feature because this is another piece of the bare metal hardware technology that is being improved by him. > Some explanation of why one would use ext4 instead of, say, > suitably-modified ramfs/tmpfs/rd/etc? The NVDIMM contents survive reboot and therefore ramfs and friends wont work with it. > Performance testing results? This is obviously avoiding kernel buffering and therefore decreasing kernel overhead for non volatile memory. Avoids useless duplication of data from the non volatile memory into regular ram and allows direct access to non volatile memory from user space in a controlled fashion. I think this should be a priority item. -- 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
