On Tue, Mar 10, 2020 at 08:36:14PM -0700, Darrick J. Wong wrote: > 1) Leave the inode flag (FS_XFLAG_DAX) as it is, and export the S_DAX > status via statx. Document that changes to FS_XFLAG_DAX do not take > effect immediately and that one must check statx to find out the real > mode. If we choose this, I would also deprecate the dax mount option; > send in my mkfs.xfs patch to make it so that you can set FS_XFLAG_DAX on > all files at mkfs time; and we can finally lay this whole thing to rest. > This is the closest to what we have today. > > 2) Withdraw FS_XFLAG_DAX entirely, and let the kernel choose based on > usage patterns, hardware heuristics, or spiteful arbitrariness. 3) Only allow changing FS_XFLAG_DAX on directories or files that do not have blocks allocated to them yet, and side step all the hard problems. Which of course still side steps the hard question of what it actually is supposed to mean..
