[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181012022108.GA2420@thunk.org>
Date: Thu, 11 Oct 2018 22:21:08 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Eric Sandeen <sandeen@...deen.net>
Cc: Dan Williams <dan.j.williams@...el.com>, Jan Kara <jack@...e.cz>,
linux-xfs <linux-xfs@...r.kernel.org>,
linux-ext4 <linux-ext4@...r.kernel.org>,
Ross Zwisler <zwisler@...nel.org>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 0/3] ext2, ext4, xfs: hard fail dax mount on unsupported
devices
On Thu, Oct 11, 2018 at 01:38:34PM -0500, Eric Sandeen wrote:
> > The different behavior between filesystems was confusing customers so
> > we had to align them, then the question was which default to pick.
> > Honestly, we came to the decision to bring ext4 in line with the xfs
> > behavior because we thought that would be easier than the alternative.
> > Dave and Christoph made repeated arguments that DAX is just a hidden
> > performance optimization that no application should rely on, so we
> > went the path of least resistance and changed the ext4 default.
>
> Ok, well, I guess we'd better reconcile "it's a hidden performance hint"
> with "if the administrator asked they must receive..." before making this
> change... cc: hch for bonus input.
And it's not so hidden if there are some applications that are
demanding that they know whether "dax" is turned on....
I don't really care, but it would nice if we settled all of these
disagreements about what dax is one way or another. Flip a coin if
necessary; ext4 isn't supporting a per-file dax flag right now since
it hasn't been clear whether or not XFS is going to drop support
(which it is claimed we can do since dax is still "experimental").
But whether it's flipping a coin or super-soakers at 20 paces, can we
please figure this out? One way or another? I'll provide some
suitable coin at LSF/MM if we can't figure it out sooner --- but I
really would prefer that it be sooner. :-)
Thanks,
- Ted
Powered by blists - more mailing lists