From: Dan Williams <dan.j.williams@intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Jan Kara <jack@suse.cz>, NVDIMM-ML <linux-nvdimm@lists.01.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Yasunori Goto <y-goto@jp.fujitsu.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Question about Experimental of Filesystem DAX.
Date: Thu, 31 May 2018 09:29:15 -0700 [thread overview]
Message-ID: <CAPcyv4jpffaM60tTdLTojhh0CDwcbVUdS8td7R6LKWM3bb15dw@mail.gmail.com> (raw)
In-Reply-To: <20180531150716.GA19764@linux.intel.com>
On Thu, May 31, 2018 at 8:07 AM, Ross Zwisler
<ross.zwisler@linux.intel.com> wrote:
> On Thu, May 31, 2018 at 11:27:33AM +0900, Yasunori Goto wrote:
>> Hello,
>>
>>
>> I would like to know about the Experimental message of Filesystem DAX.
>> --------------------------------------------------------
>> DAX enabled. Warning: EXPERIMENTAL, use at your own risk
>> --------------------------------------------------------
>>
>> AFAIK, the final issue of Filesystem DAX is metadata update problem,
>> and it is(will be?) solved by great effort of MAP_SYNC and
>> "fix dma vs truncate/hole-punch" patch set.
>> So, I suppose that the Experimental message can be removed,
>> but I'm not sure.
>>
>> Is it possible?
>> Otherwise, are there any other issues in Filesystem DAX yet?
>>
>> If this is silly question, sorry for noise....
>>
>> Thanks,
>> ---
>> Yasunori Goto
>
> Adding in the XFS and ext4 developers, as it's really their call when to
> remove this notice.
>
> We've talked about this off and on for a long while, but IMHO we should remove
> the EXPERIMENTAL warning. The last few things that we had on our TODO list
> before this was removed were:
>
> 1) Get consistent handling of the DAX mount option. We currently have this,
> as both filesystems will behave the same and fall back and remove the DAX
> mount option if it is unsupported by the block device, etc.
>
> 2) Get consistent handling of the DAX inode option. We currently have this,
> as all DAX behavior now happens through the mount option. If/when we
> re-enable the per-inode DAX flag we should do it consistently for all DAX
> enabled filesystems.
>
> 3) Make DAX work with other XFS features like reflink, etc. This one isn't
> done, but we at least disallow DAX with XFS features like reflink where it
> could be an issue. Darrick, do you still feel like we need to get these
> working together to remove EXPERIMENTAL, or are you happy enough that we're
> keeping them separated and that we're keeping user data safe?
>
> Jan and the other ext4 guys, do you have any additional things you need done
> before removing the EXPERIMENTAL warning from ext4 + DAX?
The one's on my list are:
1/ Get proper support for recovering userspace consumed poison in DAX
mappings (may not make 4.18)
2/ The DAX-DMA vs Truncate fix (queued for 4.18).
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ross Zwisler <ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
NVDIMM-ML <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>,
"Darrick J. Wong"
<darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-xfs <linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Yasunori Goto <y-goto-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
linux-ext4 <linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Question about Experimental of Filesystem DAX.
Date: Thu, 31 May 2018 09:29:15 -0700 [thread overview]
Message-ID: <CAPcyv4jpffaM60tTdLTojhh0CDwcbVUdS8td7R6LKWM3bb15dw@mail.gmail.com> (raw)
In-Reply-To: <20180531150716.GA19764-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
On Thu, May 31, 2018 at 8:07 AM, Ross Zwisler
<ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
> On Thu, May 31, 2018 at 11:27:33AM +0900, Yasunori Goto wrote:
>> Hello,
>>
>>
>> I would like to know about the Experimental message of Filesystem DAX.
>> --------------------------------------------------------
>> DAX enabled. Warning: EXPERIMENTAL, use at your own risk
>> --------------------------------------------------------
>>
>> AFAIK, the final issue of Filesystem DAX is metadata update problem,
>> and it is(will be?) solved by great effort of MAP_SYNC and
>> "fix dma vs truncate/hole-punch" patch set.
>> So, I suppose that the Experimental message can be removed,
>> but I'm not sure.
>>
>> Is it possible?
>> Otherwise, are there any other issues in Filesystem DAX yet?
>>
>> If this is silly question, sorry for noise....
>>
>> Thanks,
>> ---
>> Yasunori Goto
>
> Adding in the XFS and ext4 developers, as it's really their call when to
> remove this notice.
>
> We've talked about this off and on for a long while, but IMHO we should remove
> the EXPERIMENTAL warning. The last few things that we had on our TODO list
> before this was removed were:
>
> 1) Get consistent handling of the DAX mount option. We currently have this,
> as both filesystems will behave the same and fall back and remove the DAX
> mount option if it is unsupported by the block device, etc.
>
> 2) Get consistent handling of the DAX inode option. We currently have this,
> as all DAX behavior now happens through the mount option. If/when we
> re-enable the per-inode DAX flag we should do it consistently for all DAX
> enabled filesystems.
>
> 3) Make DAX work with other XFS features like reflink, etc. This one isn't
> done, but we at least disallow DAX with XFS features like reflink where it
> could be an issue. Darrick, do you still feel like we need to get these
> working together to remove EXPERIMENTAL, or are you happy enough that we're
> keeping them separated and that we're keeping user data safe?
>
> Jan and the other ext4 guys, do you have any additional things you need done
> before removing the EXPERIMENTAL warning from ext4 + DAX?
The one's on my list are:
1/ Get proper support for recovering userspace consumed poison in DAX
mappings (may not make 4.18)
2/ The DAX-DMA vs Truncate fix (queued for 4.18).
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>, Jan Kara <jack@suse.cz>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
NVDIMM-ML <linux-nvdimm@lists.01.org>
Subject: Re: Question about Experimental of Filesystem DAX.
Date: Thu, 31 May 2018 09:29:15 -0700 [thread overview]
Message-ID: <CAPcyv4jpffaM60tTdLTojhh0CDwcbVUdS8td7R6LKWM3bb15dw@mail.gmail.com> (raw)
In-Reply-To: <20180531150716.GA19764@linux.intel.com>
On Thu, May 31, 2018 at 8:07 AM, Ross Zwisler
<ross.zwisler@linux.intel.com> wrote:
> On Thu, May 31, 2018 at 11:27:33AM +0900, Yasunori Goto wrote:
>> Hello,
>>
>>
>> I would like to know about the Experimental message of Filesystem DAX.
>> --------------------------------------------------------
>> DAX enabled. Warning: EXPERIMENTAL, use at your own risk
>> --------------------------------------------------------
>>
>> AFAIK, the final issue of Filesystem DAX is metadata update problem,
>> and it is(will be?) solved by great effort of MAP_SYNC and
>> "fix dma vs truncate/hole-punch" patch set.
>> So, I suppose that the Experimental message can be removed,
>> but I'm not sure.
>>
>> Is it possible?
>> Otherwise, are there any other issues in Filesystem DAX yet?
>>
>> If this is silly question, sorry for noise....
>>
>> Thanks,
>> ---
>> Yasunori Goto
>
> Adding in the XFS and ext4 developers, as it's really their call when to
> remove this notice.
>
> We've talked about this off and on for a long while, but IMHO we should remove
> the EXPERIMENTAL warning. The last few things that we had on our TODO list
> before this was removed were:
>
> 1) Get consistent handling of the DAX mount option. We currently have this,
> as both filesystems will behave the same and fall back and remove the DAX
> mount option if it is unsupported by the block device, etc.
>
> 2) Get consistent handling of the DAX inode option. We currently have this,
> as all DAX behavior now happens through the mount option. If/when we
> re-enable the per-inode DAX flag we should do it consistently for all DAX
> enabled filesystems.
>
> 3) Make DAX work with other XFS features like reflink, etc. This one isn't
> done, but we at least disallow DAX with XFS features like reflink where it
> could be an issue. Darrick, do you still feel like we need to get these
> working together to remove EXPERIMENTAL, or are you happy enough that we're
> keeping them separated and that we're keeping user data safe?
>
> Jan and the other ext4 guys, do you have any additional things you need done
> before removing the EXPERIMENTAL warning from ext4 + DAX?
The one's on my list are:
1/ Get proper support for recovering userspace consumed poison in DAX
mappings (may not make 4.18)
2/ The DAX-DMA vs Truncate fix (queued for 4.18).
next prev parent reply other threads:[~2018-05-31 16:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 2:27 Question about Experimental of Filesystem DAX Yasunori Goto
2018-05-31 15:07 ` Ross Zwisler
2018-05-31 15:07 ` Ross Zwisler
2018-05-31 15:07 ` Ross Zwisler
2018-05-31 16:29 ` Dan Williams [this message]
2018-05-31 16:29 ` Dan Williams
2018-05-31 16:29 ` Dan Williams
2018-05-31 17:46 ` Darrick J. Wong
2018-05-31 17:46 ` Darrick J. Wong
2018-05-31 17:46 ` Darrick J. Wong
2018-05-31 18:26 ` Dan Williams
2018-05-31 18:26 ` Dan Williams
2018-05-31 18:26 ` Dan Williams
2018-05-31 20:25 ` Ross Zwisler
2018-05-31 20:25 ` Ross Zwisler
2018-05-31 20:25 ` Ross Zwisler
2018-06-04 1:44 ` Yasunori Goto
2018-06-04 1:44 ` Yasunori Goto
2018-06-04 1:44 ` Yasunori Goto
2018-06-04 3:51 ` Dave Chinner
2018-06-04 3:51 ` Dave Chinner
2018-06-04 3:51 ` Dave Chinner
2018-05-31 23:05 ` Dave Chinner
2018-05-31 23:05 ` Dave Chinner
2018-05-31 23:05 ` Dave Chinner
2018-06-01 1:03 ` Dan Williams
2018-06-01 1:03 ` Dan Williams
2018-06-01 1:03 ` Dan Williams
2018-06-07 14:38 ` Jan Kara
2018-06-07 14:38 ` Jan Kara
2018-06-07 14:38 ` 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=CAPcyv4jpffaM60tTdLTojhh0CDwcbVUdS8td7R6LKWM3bb15dw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=y-goto@jp.fujitsu.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 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.