From: Theodore Ts'o <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ext4@vger.kernel.org, Lukas Czerner <lczerner@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] ext4: introduce per-inode DAX flag
Date: Fri, 25 Aug 2017 11:14:45 -0400 [thread overview]
Message-ID: <20170825151445.ycf5xomoxvebgaez@thunk.org> (raw)
In-Reply-To: <20170825075415.GA748@infradead.org>
On Fri, Aug 25, 2017 at 12:54:15AM -0700, Christoph Hellwig wrote:
> > 1) Has there been any other difficulty that XFS has had due to the
> > fact that they have this DAX flag added? e.g., are there any
> > operational, or practical code maintainability issues at stake here?
> > Or is this mostly an design philosophy debate?
>
> It hasn't yet. It will create really annoying problems once we
> use raw DAX access for metadata, which I had prototype a while ago
> and plan to finnally get in in the next months.
>
> > 2) Are there any users using the DAX flag with XFS such that, if XFS
> > were to remove the DAX flag support, those users would complain
> > bitterly?
>
> I don't know of anyone that actually uses the flag. If someone did
> that would probably run into problems like changing that changing it
> on a file that's currently mmaped would crash an burn badly.
Crash and burn meaning the *kernel* will crash and burn? Or will data
be damaged?
Given that, maybe XFS should withdraw support for the DAX and hope no
one is actually using it?
- Ted
next prev parent reply other threads:[~2017-08-25 15:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 16:09 [PATCH] ext4: introduce per-inode DAX flag Lukas Czerner
2017-08-05 8:46 ` Christoph Hellwig
2017-08-07 12:12 ` Lukas Czerner
2017-08-08 9:00 ` Lukas Czerner
2017-08-11 10:01 ` Christoph Hellwig
2017-08-11 12:11 ` Lukas Czerner
2017-08-11 12:58 ` Christoph Hellwig
2017-08-11 13:41 ` Lukas Czerner
2017-08-24 18:20 ` Theodore Ts'o
2017-08-25 7:54 ` Christoph Hellwig
2017-08-25 15:14 ` Theodore Ts'o [this message]
2017-08-25 15:40 ` Christoph Hellwig
2017-08-25 16:28 ` Theodore Ts'o
2017-08-25 23:33 ` Dave Chinner
2017-08-28 7:38 ` Christoph Hellwig
2017-08-28 10:10 ` Dave Chinner
2017-08-29 15:49 ` Jan Kara
2017-08-29 22:57 ` Dave Chinner
2017-08-30 10:00 ` Jan Kara
2017-08-30 12:34 ` Christoph Hellwig
2017-08-30 15:00 ` Theodore Ts'o
2017-08-30 15:30 ` Lukas Czerner
2017-08-30 15:29 ` Jan Kara
2017-08-30 16:05 ` Jan Kara
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=20170825151445.ycf5xomoxvebgaez@thunk.org \
--to=tytso@mit.edu \
--cc=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.