From: Jeff Moyer <jmoyer@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-nvdimm@ml01.01.org, linux-block@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Mon, 16 Jan 2017 15:00:41 -0500 [thread overview]
Message-ID: <x49wpduzseu.fsf@dhcp-25-115.bos.redhat.com> (raw)
In-Reply-To: <20170114082621.GC10498@birch.djwong.org> (Darrick J. Wong's message of "Sat, 14 Jan 2017 00:26:21 -0800")
"Darrick J. Wong" <darrick.wong@oracle.com> writes:
>> - Whenever you mount a filesystem with DAX, it spits out a message that says
>> "DAX enabled. Warning: EXPERIMENTAL, use at your own risk". What criteria
>> needs to be met for DAX to no longer be considered experimental?
>
> For XFS I'd like to get reflink working with it, for starters.
What do you mean by this, exactly? When Dave outlined the requirements
for PMEM_IMMUTABLE, it was very clear that metadata updates would not be
possible. And would you really cosider this a barrier to marking dax
fully supported? I wouldn't.
> We probably need a bunch more verification work to show that file IO
> doesn't adopt any bad quirks having turned on the per-inode DAX flag.
Can you be more specific? We have ltp and xfstests. If you have some
mkfs/mount options that you think should be tested, speak up. Beyond
that, if it passes ./check -g auto and ltp, are we good?
-Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Moyer <jmoyer@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-nvdimm@ml01.01.org, linux-block@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Mon, 16 Jan 2017 15:00:41 -0500 [thread overview]
Message-ID: <x49wpduzseu.fsf@dhcp-25-115.bos.redhat.com> (raw)
In-Reply-To: <20170114082621.GC10498@birch.djwong.org> (Darrick J. Wong's message of "Sat, 14 Jan 2017 00:26:21 -0800")
"Darrick J. Wong" <darrick.wong@oracle.com> writes:
>> - Whenever you mount a filesystem with DAX, it spits out a message that says
>> "DAX enabled. Warning: EXPERIMENTAL, use at your own risk". What criteria
>> needs to be met for DAX to no longer be considered experimental?
>
> For XFS I'd like to get reflink working with it, for starters.
What do you mean by this, exactly? When Dave outlined the requirements
for PMEM_IMMUTABLE, it was very clear that metadata updates would not be
possible. And would you really cosider this a barrier to marking dax
fully supported? I wouldn't.
> We probably need a bunch more verification work to show that file IO
> doesn't adopt any bad quirks having turned on the per-inode DAX flag.
Can you be more specific? We have ltp and xfstests. If you have some
mkfs/mount options that you think should be tested, speak up. Beyond
that, if it passes ./check -g auto and ltp, are we good?
-Jeff
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-01-16 20:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 0:20 [LSF/MM TOPIC] Future direction of DAX Ross Zwisler
2017-01-14 0:20 ` Ross Zwisler
2017-01-14 0:20 ` Ross Zwisler
[not found] ` <20170114002008.GA25379-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-01-14 8:26 ` Darrick J. Wong
2017-01-14 8:26 ` Darrick J. Wong
2017-01-14 8:26 ` Darrick J. Wong
2017-01-16 0:19 ` Viacheslav Dubeyko
2017-01-16 0:19 ` Viacheslav Dubeyko
2017-01-16 0:19 ` Viacheslav Dubeyko
2017-01-16 20:00 ` Jeff Moyer [this message]
2017-01-16 20:00 ` Jeff Moyer
2017-01-17 1:50 ` Darrick J. Wong
2017-01-17 1:50 ` Darrick J. Wong
2017-01-17 2:42 ` Dan Williams
2017-01-17 2:42 ` Dan Williams
[not found] ` <20170117015033.GD10498-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2017-01-17 7:57 ` Christoph Hellwig
2017-01-17 7:57 ` Christoph Hellwig
2017-01-17 7:57 ` Christoph Hellwig
2017-01-17 14:54 ` Jeff Moyer
2017-01-17 14:54 ` Jeff Moyer
[not found] ` <x49mvep4tzw.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2017-01-17 15:06 ` Christoph Hellwig
2017-01-17 15:06 ` Christoph Hellwig
2017-01-17 15:06 ` Christoph Hellwig
[not found] ` <20170117150638.GA3747-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-01-17 16:07 ` Jeff Moyer
2017-01-17 16:07 ` Jeff Moyer
2017-01-17 16:07 ` Jeff Moyer
2017-01-17 15:59 ` [Lsf-pc] " Jan Kara
2017-01-17 15:59 ` Jan Kara
2017-01-17 15:59 ` Jan Kara
2017-01-17 16:56 ` Dan Williams
2017-01-17 16:56 ` Dan Williams
2017-01-17 16:56 ` Dan Williams
2017-01-18 0:03 ` Kani, Toshimitsu
2017-01-18 0:03 ` Kani, Toshimitsu
2017-01-18 0:03 ` Kani, Toshimitsu
2017-01-18 5:25 ` willy
2017-01-18 5:25 ` willy
2017-01-18 5:25 ` willy
2017-01-18 6:01 ` Dan Williams
2017-01-18 6:01 ` Dan Williams
2017-01-18 6:01 ` Dan Williams
2017-01-18 6:07 ` willy
2017-01-18 6:07 ` willy
2017-01-18 6:07 ` willy
2017-01-18 6:25 ` Dan Williams
2017-01-18 6:25 ` Dan Williams
2017-01-18 6:25 ` Dan Williams
2017-01-18 17:22 ` Ross Zwisler
2017-01-18 17:22 ` Ross Zwisler
2017-01-18 17:22 ` Ross Zwisler
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=x49wpduzseu.fsf@dhcp-25-115.bos.redhat.com \
--to=jmoyer@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ross.zwisler@linux.intel.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.