I haven't heard from anyone on qemu-devel. There are a lot of vNVDIMM experts here and I'm hoping that someone here may throw some light.
-BT ----- Forwarded Message ----- From: [email protected] <[email protected]>To: [email protected] <[email protected]>Sent: Friday, February 15, 2019, 12:09:31 PM ESTSubject: Why only devdax guarantees guest data persistence ? Text from "docs/nvdimm.txt" says: Guest Data Persistence ---------------------- Though QEMU supports multiple types of vNVDIMM backends on Linux, currently the only one that can guarantee the guest write persistence is the device DAX on the real NVDIMM device (e.g., /dev/dax0.0), to which all guest access do not involve any host-side kernel cache. I think here "host-side kernel cache" imply "page cache". Why does fsdax NOT have the same persistence guarantees as devdax for vNVDIMM? Both the modes avoid using page cache then why is devdax explicitly called out? -BT _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
