On Tue, Jul 25, 2017 at 05:15:10PM -0700, Dan Williams wrote: > We're in the process of walking back and potentially deprecating the > use of the dax mount option for xfs and ext4 since dax can have > negative performance implications if page cache memory happens to be > faster than pmem. It should be limited to applications that > specifically want the semantic, not globally enabled for the entire > mount. xfs has went ahead and added the XFS_DIFLAG2_DAX indoe flag for > per-inode enabling of dax. > > I'm wondering if any new filesystem that adds dax support at this > point should do so with inode flags and not a mount option? That tradeoff is not one that the application should make, but one that should depend on the storage medium. To make things worse it might also depend on the type of access. E.g. with certain media it makes a lot of sense to cache writes in the page cache, but generally not reads. I've been spending some time to analyze how that could be done, but I've not made real progress on it. XFS_DIFLAG2_DAX is unfortunately totally unhelpful with that.
