From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Soccer Liu <soccer_liu@yahoo.com>
Cc: "Linux-nvdimm@lists.01.org" <Linux-nvdimm@lists.01.org>
Subject: Re: DAX enabled. Warning: EXPERIMENTAL, use at your own risk
Date: Wed, 13 Sep 2017 13:50:26 -0600 [thread overview]
Message-ID: <20170913195026.GA26069@linux.intel.com> (raw)
In-Reply-To: <83993302.1433078.1505327170801@mail.yahoo.com>
On Wed, Sep 13, 2017 at 06:26:10PM +0000, Soccer Liu wrote:
>
> Hi:
> During my debugging, I kept seeing this message from the DAX enabled mount
> operation.
>
> [ 0.757990] EXT4-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at your own risk
>
> I am wondering how far this DAX feature is still away from becoming a
> "non-experimental" feature. (Another way of asking my questions: are there
> any major issues that's blocking it?)
We talked about this a bit as a group during my LSF/MM talk this year:
https://lwn.net/Articles/717953/
Essentially the consensus was that we need to make the XFS and ext4 mount
options consistent and get reflink + DAX in a better state. We also probably
figure out the per-DAX inode issues that have recently been under discussion:
https://lkml.org/lkml/2017/9/6/529
There will always be work to do, but I think those are the things that are
standing between us and removing the EXPERIMENTAL warning.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-09-13 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83993302.1433078.1505327170801.ref@mail.yahoo.com>
2017-09-13 18:26 ` DAX enabled. Warning: EXPERIMENTAL, use at your own risk Soccer Liu
2017-09-13 19:50 ` Ross Zwisler [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=20170913195026.GA26069@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=Linux-nvdimm@lists.01.org \
--cc=soccer_liu@yahoo.com \
/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