From: Christoph Hellwig <hch@lst.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dan Williams <dan.j.williams@intel.com>, Jan Kara <jack@suse.cz>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Ross Zwisler <zwisler@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/3] ext2, ext4, xfs: hard fail dax mount on unsupported devices
Date: Fri, 12 Oct 2018 10:21:54 +0200 [thread overview]
Message-ID: <20181012082154.GB30154@lst.de> (raw)
In-Reply-To: <5a8e54e8-4845-1c85-e4e9-0b9b551a9ce2@sandeen.net>
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.
I don't really care too mouch on the mount options, the important bit
was the application behavior.
I fully agree with Dan that we should have the same behavior for every
file system, though.
next prev parent reply other threads:[~2018-10-12 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 19:32 [PATCH 0/3] ext2, ext4, xfs: hard fail dax mount on unsupported devices Eric Sandeen
2018-10-08 19:32 ` [PATCH 1/3] " Eric Sandeen
2018-10-08 22:10 ` Dave Chinner
2018-10-08 19:32 ` [PATCH 2/3] ext4: " Eric Sandeen
2018-12-04 5:48 ` Theodore Y. Ts'o
2018-10-08 19:32 ` [PATCH 3/3] ext2: " Eric Sandeen
2018-10-11 10:36 ` [PATCH 0/3] ext2, ext4, xfs: " Jan Kara
2018-10-11 18:08 ` Dan Williams
2018-10-11 18:38 ` Eric Sandeen
2018-10-12 2:21 ` Theodore Y. Ts'o
2018-10-12 8:21 ` Christoph Hellwig [this message]
2018-10-13 16:05 ` Ross Zwisler
2018-10-17 19:42 ` Eric Sandeen
2018-10-17 19:51 ` Ross Zwisler
2018-10-17 19:52 ` Dan Williams
2018-10-17 21:31 ` Jeff Moyer
2018-10-17 21:44 ` Dan Williams
2018-10-18 1:05 ` Dave Chinner
2018-10-18 2:01 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181012082154.GB30154@lst.de \
--to=hch@lst.de \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=zwisler@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).