Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-27 Thread Jared Hulbert
On Mon, Jan 25, 2016 at 1:18 PM, Jared Hulbert wrote: > On Mon, Jan 25, 2016 at 8:52 AM, Matthew Wilcox wrote: >> On Sun, Jan 24, 2016 at 01:03:49AM -0800, Jared Hulbert wrote: >>> I our defense we didn't know we were sinning at the time. >> >> Fair enough. Cache flushing is Hard. >> >>> Can you

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-25 Thread Jared Hulbert
On Mon, Jan 25, 2016 at 8:52 AM, Matthew Wilcox wrote: > On Sun, Jan 24, 2016 at 01:03:49AM -0800, Jared Hulbert wrote: >> I our defense we didn't know we were sinning at the time. > > Fair enough. Cache flushing is Hard. > >> Can you walk me through the cache flushing hole? How is it okay on >>

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-25 Thread Matthew Wilcox
On Sun, Jan 24, 2016 at 01:03:49AM -0800, Jared Hulbert wrote: > I our defense we didn't know we were sinning at the time. Fair enough. Cache flushing is Hard. > Can you walk me through the cache flushing hole? How is it okay on > X86 but not VIVT archs? I'm missing something obvious here. >

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-24 Thread Jared Hulbert
I our defense we didn't know we were sinning at the time. Can you walk me through the cache flushing hole? How is it okay on X86 but not VIVT archs? I'm missing something obvious here. I thought earlier that vm_insert_mixed() handled the necessary flushing. Is that even the part you are worrie

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-22 Thread Matthew Wilcox
On Fri, Jan 22, 2016 at 01:48:08PM +, Chris Brandt wrote: > I believe the motivation for the new DAX code was being able to > read/write data directly to specific physical memory. However, with > the AXFS file system, XIP file mapping was mostly beneficial for direct > access to executable code

RE: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-22 Thread Chris Brandt
ew Wilcox ; Andrew Morton ; Carsten Otte ; Chris Brandt Subject: RE: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation Hi Jared, The old filemap_xip code was living in a state of sin ;-) It was writing to the kernel's mapping of an address, and then not flushing the cache

RE: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-22 Thread Wilcox, Matthew R
Otte; Chris Brandt Subject: Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation HI! I've been out of the community for a while, but I'm trying to step back in here and catch up with some of my old areas of specialty. Couple questions, sorry to drag up suc

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2016-01-21 Thread Jared Hulbert
HI! I've been out of the community for a while, but I'm trying to step back in here and catch up with some of my old areas of specialty. Couple questions, sorry to drag up such old conversations. The DAX documentation that made it into kernel 4.0 has the following line "The DAX code does not wor

Re: [PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2015-01-12 Thread Andrew Morton
On Fri, 24 Oct 2014 17:20:42 -0400 Matthew Wilcox wrote: > Based on the original XIP documentation, this documents the current > state of affairs, and includes instructions on how users can enable DAX > if their devices and kernel support it. Nice ;) -- To unsubscribe from this list: send the l

[PATCH v12 10/20] dax: Replace XIP documentation with DAX documentation

2014-10-24 Thread Matthew Wilcox
From: Matthew Wilcox Based on the original XIP documentation, this documents the current state of affairs, and includes instructions on how users can enable DAX if their devices and kernel support it. Signed-off-by: Matthew Wilcox Reviewed-by: Randy Dunlap --- Documentation/filesystems/00-IND