From patchwork Fri Feb 7 20:26:45 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Vivek Goyal X-Patchwork-Id: 11371221 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 2617E2D34 for ; Fri, 7 Feb 2020 20:27:14 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0017C21741 for ; Fri, 7 Feb 2020 20:27:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="cNn2knW7" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0017C21741 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id AA89410FC3599; Fri, 7 Feb 2020 12:30:30 -0800 (PST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=205.139.110.120; helo=us-smtp-1.mimecast.com; envelope-from=vgoyal@redhat.com; receiver= Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 10FB710FC3592 for ; Fri, 7 Feb 2020 12:30:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581107229; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=1xKgewOcOXOvkG5+BQKERYsXsHqhJlKwJrAB1sWMGeI=; b=cNn2knW7Cay/bn/vupLpq/F2X3DntwGacmqjf4cLEL0CmHma4Xdxd7SXIpYyDc60CO3lB6 SF8nQwC0d0zdA3mjMX5NNniHsxGXxEFScU6XAHenRzH9k0xCRN7HKPDVr7VHOi3ynmgm6I 8BsUhObaBXqtWDn6DBg8CKhMTJ6kgBw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-266-i6v90NH-MISjJ_WKwZ5_xA-1; Fri, 07 Feb 2020 15:27:07 -0500 X-MC-Unique: i6v90NH-MISjJ_WKwZ5_xA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BE59A8010E7; Fri, 7 Feb 2020 20:27:05 +0000 (UTC) Received: from horse.redhat.com (unknown [10.18.25.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id 087A9100164D; Fri, 7 Feb 2020 20:27:03 +0000 (UTC) Received: by horse.redhat.com (Postfix, from userid 10451) id 89CE6220A24; Fri, 7 Feb 2020 15:27:02 -0500 (EST) From: Vivek Goyal To: linux-fsdevel@vger.kernel.org, linux-nvdimm@lists.01.org, hch@infradead.org, dan.j.williams@intel.com Subject: [PATCH v3 0/7] dax,pmem: Provide a dax operation to zero range of memory Date: Fri, 7 Feb 2020 15:26:45 -0500 Message-Id: <20200207202652.1439-1-vgoyal@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Message-ID-Hash: ENLCVEPKNFXETJITYIJFUKZTX6ODU6BR X-Message-ID-Hash: ENLCVEPKNFXETJITYIJFUKZTX6ODU6BR X-MailFrom: vgoyal@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: dm-devel@redhat.com X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: 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. 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(-)