2 ms·
> "DAX is also working in modern kernels, and it was a relatively trivial job to implement DAX." What is DAX? Is that like an execute-in-place feature that me
by wyldfire 10y ago
> "DAX is also working in modern kernels, and it was a relatively trivial job to implement DAX."
What is DAX? Is that like an execute-in-place feature that means we don't need paging to execute code?
If so, is this feature generally useful for all QEmu use cases?
- rwmj 10y agoIn real hardware, DAX comes in two parts. There is an NVDIMM device (basically ordinary DRAM, but backed by additional flash chips so it preserves its contents when powered off). NVDIMMs work at RAM speeds so although you can use them as fast block devices, it's better to direct map them to avoid the block layer completely. The other part is a filesystem implementation (I have used ext4, but xfs exists too) which lets you mmap files directly if they come from a device which is backed by NVDIMMs. Also execute-in-place for binaries (like the old XIP support in ext2 which is obsoleted by DAX). QEMU has a virtual NVDIMM ("vNVDIMM") so you can test this without needing the real NVDIMM hardware. But in this case it's also a useful way to reduce memory usage, since you're avoiding the block layer and page cache in the guest. That's the theory. Although I've been able to make it function correctly, I didn't observe any great improvements in speed or memory usage (see the paper for details). Here is a patch which adds DAX support to libguestfs which should give you some ideas how to try out DAX in QEMU: https://www.redhat.com/archives/libguestfs/2016-May/msg00138.html https://www.redhat.com/archives/libguestfs/2016-May/msg00138...
- deleted 10y ago[deleted]