[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150903164453.GA10341@linux.intel.com>
Date: Thu, 3 Sep 2015 10:44:53 -0600
From: Ross Zwisler <ross.zwisler@...ux.intel.com>
To: Boaz Harrosh <boaz@...xistor.com>
Cc: Ross Zwisler <ross.zwisler@...ux.intel.com>,
Christoph Hellwig <hch@....de>,
Dave Chinner <david@...morbit.com>,
Andrew Morton <akpm@...l.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
linux-nvdimm@...ts.01.org, Peter Zijlstra <peterz@...radead.org>,
x86@...nel.org, Hugh Dickins <hughd@...gle.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Ingo Molnar <mingo@...hat.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
"H. Peter Anvin" <hpa@...or.com>, linux-fsdevel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH] dax, pmem: add support for msync
On Thu, Sep 03, 2015 at 09:32:02AM +0300, Boaz Harrosh wrote:
> On 09/02/2015 10:04 PM, Ross Zwisler wrote:
> > On Tue, Sep 01, 2015 at 03:18:41PM +0300, Boaz Harrosh wrote:
> <>
> >> Apps expect all these to work:
> >> 1. open mmap m-write msync ... close
> >> 2. open mmap m-write fsync ... close
> >> 3. open mmap m-write unmap ... fsync close
> >>
> >> 4. open mmap m-write sync ...
> >
> > So basically you made close have an implicit fsync? What about the flow that
> > looks like this:
> >
> > 5. open mmap close m-write
> >
>
> What? no, close means ummap because you need a file* attached to your vma
>
> And you miss-understood me, the vm_opts->close is the *unmap* operation not
> the file::close() operation.
>
> I meant memory-cl_flush on unmap before the vma goes away.
Ah, got it, thanks for the clarification.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists