Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-18 Thread Ross Zwisler
On Tue, Jan 17, 2017 at 09:25:33PM -0800, wi...@bombadil.infradead.org wrote: > On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote: > > We still have a lot of work to do, though, and I'd like to propose a > > discussion > > around what features people would like to see enabled in the com

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Dan Williams
On Tue, Jan 17, 2017 at 10:07 PM, wrote: > On Tue, Jan 17, 2017 at 10:01:30PM -0800, Dan Williams wrote: >> >> - Jan suggested [2] that we could use the radix tree as a cache to >> >> service DAX >> >> faults without needing to call into the filesystem. Are there any >> >> issues >> >> wit

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread willy
On Tue, Jan 17, 2017 at 10:01:30PM -0800, Dan Williams wrote: > >> - Jan suggested [2] that we could use the radix tree as a cache to service > >> DAX > >> faults without needing to call into the filesystem. Are there any issues > >> with this approach, and should we move forward with it as a

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Dan Williams
On Tue, Jan 17, 2017 at 9:25 PM, wrote: > On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote: >> We still have a lot of work to do, though, and I'd like to propose a >> discussion >> around what features people would like to see enabled in the coming year as >> well as what what use ca

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread willy
On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote: > We still have a lot of work to do, though, and I'd like to propose a > discussion > around what features people would like to see enabled in the coming year as > well as what what use cases their customers have that we might not be aw

Re: [Lsf-pc] [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Kani, Toshimitsu
On Tue, 2017-01-17 at 16:59 +0100, Jan Kara wrote: > On Fri 13-01-17 17:20:08, Ross Zwisler wrote: : > > - If I recall correctly, at one point Dave Chinner suggested that > > we change - If I recall correctly, at one point Dave Chinner > > suggested that we change   DAX so that I/O would use cache

Re: [Lsf-pc] [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Dan Williams
On Tue, Jan 17, 2017 at 7:59 AM, Jan Kara wrote: > On Fri 13-01-17 17:20:08, Ross Zwisler wrote: >> - The DAX fsync/msync model was built for platforms that need to flush dirty >> processor cache lines in order to make data durable on NVDIMMs. There >> exist >> platforms, however, that are s

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Jeff Moyer
Christoph Hellwig writes: > On Tue, Jan 17, 2017 at 09:54:27AM -0500, Jeff Moyer wrote: >> I spoke with Dave before the holidays, and he indicated that >> PMEM_IMMUTABLE would be an acceptable solution to allowing applications >> to flush data completely from userspace. I know this subject has b

Re: [Lsf-pc] [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Jan Kara
On Fri 13-01-17 17:20:08, Ross Zwisler wrote: > - The DAX fsync/msync model was built for platforms that need to flush dirty > processor cache lines in order to make data durable on NVDIMMs. There exist > platforms, however, that are set up so that the processor caches are > effectively part

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Christoph Hellwig
On Tue, Jan 17, 2017 at 09:54:27AM -0500, Jeff Moyer wrote: > I spoke with Dave before the holidays, and he indicated that > PMEM_IMMUTABLE would be an acceptable solution to allowing applications > to flush data completely from userspace. I know this subject has been > beaten to death, but would

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-17 Thread Jeff Moyer
Christoph Hellwig writes: > On Mon, Jan 16, 2017 at 05:50:33PM -0800, Darrick J. Wong wrote: >> I wouldn't consider it a barrier in general (since ext4 also prints >> EXPERIMENTAL warnings for DAX), merely one for XFS. I don't even think >> it's that big of a hurdle -- afaict XFS ought to be abl

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-16 Thread Christoph Hellwig
On Mon, Jan 16, 2017 at 05:50:33PM -0800, Darrick J. Wong wrote: > I wouldn't consider it a barrier in general (since ext4 also prints > EXPERIMENTAL warnings for DAX), merely one for XFS. I don't even think > it's that big of a hurdle -- afaict XFS ought to be able to achieve this > by modifying

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-16 Thread Dan Williams
On Mon, Jan 16, 2017 at 5:50 PM, Darrick J. Wong wrote: > On Mon, Jan 16, 2017 at 03:00:41PM -0500, Jeff Moyer wrote: >> "Darrick J. Wong" writes: >> >> >> - Whenever you mount a filesystem with DAX, it spits out a message that >> >> says >> >> "DAX enabled. Warning: EXPERIMENTAL, use at your

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-16 Thread Darrick J. Wong
On Mon, Jan 16, 2017 at 03:00:41PM -0500, Jeff Moyer wrote: > "Darrick J. Wong" 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

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-16 Thread Jeff Moyer
"Darrick J. Wong" 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 worki

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-15 Thread Viacheslav Dubeyko
On Sat, 2017-01-14 at 00:26 -0800, Darrick J. Wong wrote: > Some day we'll start designing a pmem-native fs, I guess. :P There are research efforts in this direction already ([1]-[15]). The latest one is NOVA, as far as I can see. But, frankly speaking, I believe that we need in new hardware pa

Re: [LSF/MM TOPIC] Future direction of DAX

2017-01-14 Thread Darrick J. Wong
On Fri, Jan 13, 2017 at 05:20:08PM -0700, Ross Zwisler wrote: > This past year has seen a lot of new DAX development. We have added support > for fsync/msync, moved to the new iomap I/O data structure, introduced radix > tree based locking, re-enabled PMD support (twice!), and have fixed a bunch o

[LSF/MM TOPIC] Future direction of DAX

2017-01-13 Thread Ross Zwisler
This past year has seen a lot of new DAX development. We have added support for fsync/msync, moved to the new iomap I/O data structure, introduced radix tree based locking, re-enabled PMD support (twice!), and have fixed a bunch of bugs. We still have a lot of work to do, though, and I'd like to