From: Jan Kara <jack@suse.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-nvdimm@lists.01.org
Subject: Re: [LSF/MM TOPIC] Standardizing semantics around the per-file DAX flag
Date: Tue, 19 Feb 2019 13:35:36 +0100 [thread overview]
Message-ID: <20190219123536.GA27420@quack2.suse.cz> (raw)
In-Reply-To: <20190213164039.GA16285@mit.edu>
On Wed 13-02-19 11:40:39, Theodore Y. Ts'o wrote:
> There's been a long-term disagreement about how the per-file DAX flag
> should work.
>
> * Should it exist at all?
> * What happens when the DAX flag is cleared?
> * Should it be not allowed and return an error?
> (Or maybe only if the file is otherwise opened anywhere in the system?)
> * Should it only takes effect when the file system is unmounted,
> or when the inode drops out of the inode cache?
> * Should we remove the flag entirely and make it be something the
> system automagically infers?
>
> I had hoped consensus would be achieved before the ext4 per-file DAX
> flag lands, but it hasn't for a *long* time. Technically the DAX flag
> is "experimental", which technically means it could be removed ---
> although I suspect at this point, it would break some userspace, so
> our options about how to adjust the semantics of the flag are probably
> constrained.
Well, there's no filesystem that would really support the DAX flag
currently (XFS accepts it, stores it, but does nothing with it). So I think
we are reasonably free in defining the semantics. Also I think this is
closely related to Dan's topic "What should be done to remove experimental
tag from DAX" (or however it was called).
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-02-19 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 16:40 [LSF/MM TOPIC] Standardizing semantics around the per-file DAX flag Theodore Y. Ts'o
2019-02-19 12:35 ` Jan Kara [this message]
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=20190219123536.GA27420@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tytso@mit.edu \
/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).