[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4hmCsNOZPEAzOLxhFCQpyaG0_9TJvJnyuytQAVEU7_wbA@mail.gmail.com>
Date: Sun, 25 Nov 2018 12:59:59 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Huaisheng Ye <yehs2007@...o.com>
Cc: linux-nvdimm <linux-nvdimm@...ts.01.org>,
Alasdair Kergon <agk@...hat.com>,
Mike Snitzer <snitzer@...hat.com>,
device-mapper development <dm-devel@...hat.com>,
Matthew Wilcox <willy@...radead.org>, zwisler@...nel.org,
Jan Kara <jack@...e.cz>, Dave Jiang <dave.jiang@...el.com>,
Vishal L Verma <vishal.l.verma@...el.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
NingTing Cheng <chengnt@...ovo.com>,
Huaisheng Ye <yehs1@...ovo.com>
Subject: Re: [RFC PATCH v2 0/3] realize dax_operations for dm-snapshot
On Tue, Nov 20, 2018 at 7:27 PM Huaisheng Ye <yehs2007@...o.com> wrote:
>
> From: Huaisheng Ye <yehs1@...ovo.com>
>
> Changes
> v1->v2:
> Add NULL funtions for origin_dax_direct_access and
> origin_dax_copy_from/to_iter in order to avoid building
> error when CONFIG_DAX_DRIVER has NOT been enabled.
>
> [v1]: https://lkml.org/lkml/2018/11/20/759
>
> This series patches are used to realize the dax_operations for dm-snapshot
> with persistent memory device.
How does this interact with mmap write faults if the mapping is dax
and the page needs to be cow'd?
Powered by blists - more mailing lists