From: Dan Williams <dan.j.williams@intel.com>
To: Huaisheng Ye <yehs2007@zoho.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
zwisler@kernel.org, Jan Kara <jack@suse.cz>,
Dave Jiang <dave.jiang@intel.com>,
Vishal L Verma <vishal.l.verma@intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NingTing Cheng <chengnt@lenovo.com>,
Huaisheng Ye <yehs1@lenovo.com>
Subject: Re: [RFC PATCH v2 0/3] realize dax_operations for dm-snapshot
Date: Sun, 25 Nov 2018 12:59:59 -0800 [thread overview]
Message-ID: <CAPcyv4hmCsNOZPEAzOLxhFCQpyaG0_9TJvJnyuytQAVEU7_wbA@mail.gmail.com> (raw)
In-Reply-To: <20181121032702.3048-1-yehs2007@zoho.com>
On Tue, Nov 20, 2018 at 7:27 PM Huaisheng Ye <yehs2007@zoho.com> wrote:
>
> From: Huaisheng Ye <yehs1@lenovo.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?
next prev parent reply other threads:[~2018-11-25 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 3:26 [RFC PATCH v2 0/3] realize dax_operations for dm-snapshot Huaisheng Ye
2018-11-21 3:27 ` [RFC PATCH v2 1/3] dm: enable " Huaisheng Ye
2018-11-21 3:27 ` [RFC PATCH v2 2/3] dm: expand hc_map in mapped_device for lack of map Huaisheng Ye
2018-11-21 3:27 ` [RFC PATCH v2 3/3] dm: expand valid types for dm-ioctl Huaisheng Ye
2018-11-25 20:59 ` Dan Williams [this message]
2018-11-28 14:27 ` [External] Re: [RFC PATCH v2 0/3] realize dax_operations for dm-snapshot Huaisheng HS1 Ye
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=CAPcyv4hmCsNOZPEAzOLxhFCQpyaG0_9TJvJnyuytQAVEU7_wbA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=agk@redhat.com \
--cc=chengnt@lenovo.com \
--cc=dave.jiang@intel.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=snitzer@redhat.com \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
--cc=yehs1@lenovo.com \
--cc=yehs2007@zoho.com \
--cc=zwisler@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).