From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-nvdimm@lists.01.org,
hch@infradead.org, dan.j.williams@intel.com
Cc: dm-devel@redhat.com
Subject: Re: [PATCH v3 0/7] dax,pmem: Provide a dax operation to zero range of memory
Date: Fri, 14 Feb 2020 07:57:17 -0500 [thread overview]
Message-ID: <20200214125717.GA18654@redhat.com> (raw)
In-Reply-To: <20200207202652.1439-1-vgoyal@redhat.com>
On Fri, Feb 07, 2020 at 03:26:45PM -0500, Vivek Goyal wrote:
> Hi,
>
> This is V3 of patches. I have dropped RFC tag from the series as it
> looks like there is agreement on the interface. These patches are also
> available at.
Hi Dan, Christoph,
Ping for this patch series. How does it look? Do you have concerns?
If not, it will be good if this is merged.
Thanks
Vivek
>
> https://github.com/rhvgoyal/linux/commits/dax-zero-range-v3
>
> I posted previous versions here.
>
> v2:
> https://lore.kernel.org/linux-fsdevel/20200203200029.4592-1-vgoyal@redhat.com/
> v1:
> https://lore.kernel.org/linux-fsdevel/20200123165249.GA7664@redhat.com/
>
> Changes since V2:
>
> Primarily took care of comments from Christoph.
>
> - Changed zero_copy_range() parameters to pass dax device offset as u64.
> - Fixed comment which says current interface only supports zeroing
> with-in page.
> - Refactored pmem_do_bvec() and reused write side of code in
> zero_page_range().
> - Removed generic_dax_zero_page_range()
> - Fixed s390 dcssblk.c compilation issue.
>
> Please review.
>
> Thanks
> Vivek
>
> Vivek Goyal (7):
> pmem: Add functions for reading/writing page to/from pmem
> pmem: Enable pmem_do_write() to deal with arbitrary ranges
> dax, pmem: Add a dax operation zero_page_range
> s390,dcssblk,dax: Add dax zero_page_range operation to dcssblk driver
> dm,dax: Add dax zero_page_range operation
> dax,iomap: Start using dax native zero_page_range()
> dax,iomap: Add helper dax_iomap_zero() to zero a range
>
> drivers/dax/super.c | 19 ++++++
> drivers/md/dm-linear.c | 21 +++++++
> drivers/md/dm-log-writes.c | 19 ++++++
> drivers/md/dm-stripe.c | 26 ++++++++
> drivers/md/dm.c | 31 ++++++++++
> drivers/nvdimm/pmem.c | 112 ++++++++++++++++++++++++----------
> drivers/s390/block/dcssblk.c | 17 ++++++
> fs/dax.c | 53 ++++------------
> fs/iomap/buffered-io.c | 9 +--
> include/linux/dax.h | 20 ++----
> include/linux/device-mapper.h | 3 +
> 11 files changed, 235 insertions(+), 95 deletions(-)
>
> --
> 2.20.1
>
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
prev parent reply other threads:[~2020-02-14 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 20:26 [PATCH v3 0/7] dax,pmem: Provide a dax operation to zero range of memory Vivek Goyal
2020-02-07 20:26 ` [PATCH v3 1/7] pmem: Add functions for reading/writing page to/from pmem Vivek Goyal
2020-02-17 13:21 ` Christoph Hellwig
2020-02-17 18:04 ` Vivek Goyal
2020-02-07 20:26 ` [PATCH v3 2/7] pmem: Enable pmem_do_write() to deal with arbitrary ranges Vivek Goyal
2020-02-17 13:23 ` Christoph Hellwig
2020-02-17 14:59 ` Vivek Goyal
2020-02-07 20:26 ` [PATCH v3 3/7] dax, pmem: Add a dax operation zero_page_range Vivek Goyal
2020-02-17 13:26 ` Christoph Hellwig
2020-02-17 18:08 ` Vivek Goyal
2020-02-07 20:26 ` [PATCH v3 4/7] s390,dcssblk,dax: Add dax zero_page_range operation to dcssblk driver Vivek Goyal
2020-02-10 20:53 ` Gerald Schaefer
2020-02-11 15:11 ` Vivek Goyal
2020-02-11 15:49 ` Gerald Schaefer
2020-02-07 20:26 ` [PATCH v3 5/7] dm,dax: Add dax zero_page_range operation Vivek Goyal
2020-02-07 20:26 ` [PATCH v3 6/7] dax,iomap: Start using dax native zero_page_range() Vivek Goyal
2020-02-17 13:26 ` Christoph Hellwig
2020-02-07 20:26 ` [PATCH v3 7/7] dax,iomap: Add helper dax_iomap_zero() to zero a range Vivek Goyal
2020-02-17 13:27 ` Christoph Hellwig
2020-02-14 12:57 ` Vivek Goyal [this message]
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=20200214125717.GA18654@redhat.com \
--to=vgoyal@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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).