On Tue, Sep 26, 2017 at 09:09:57PM +1000, Dave Chinner wrote: > Well, quite frankly, I never wanted the mount option for XFS. It was > supposed to be for initial testing only, then we'd /always/ use the > the inode flags. For a filesystem to default to using DAX, we > set the DAX flag on the root inode at mkfs time, and then everything > inode flag based just works. And I deeply fundamentally disagree. The mount option is a nice enough big hammer to try a mode without encoding nitty gritty details into the application ABI. The per-inode persistent flag is the biggest nightmare ever, as we see in all these discussions about it. What does it even mean? Right now it forces direct addressing as long as the underlying media supports that. But what about media that you directly access but you really don't want to because it's really slow? Or media that is so god damn fast that you never want to buffer? Or media where you want to buffer for writes (or at least some of them) but not for reads? It encodes a very specific mechanism for an early direct access implementation into the ABI. What we really need is for applications to declare an intent, not specify a particular mechanism. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
