From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7C5091A1E53 for ; Wed, 31 Aug 2016 14:36:09 -0700 (PDT) Date: Wed, 31 Aug 2016 15:36:07 -0600 From: Ross Zwisler Subject: Re: [PATCH v2 0/9] re-enable DAX PMD support Message-ID: <20160831213607.GA6921@linux.intel.com> References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160830230150.GA12173@linux.intel.com> <1472674799.2092.19.camel@hpe.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1472674799.2092.19.camel@hpe.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: "Kani, Toshimitsu" Cc: "tytso@mit.edu" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "linux-nvdimm@lists.01.org" , "david@fromorbit.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "adilger.kernel@dilger.ca" , "viro@zeniv.linux.org.uk" , "jack@suse.com" , "linux-fsdevel@vger.kernel.org" , "linux-ext4@vger.kernel.org" List-ID: On Wed, Aug 31, 2016 at 08:20:48PM +0000, Kani, Toshimitsu wrote: > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote: > > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > > > = > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix > > > tree based locking.=A0=A0This series allows DAX PMDs to participate in > > > the DAX radix tree based locking scheme so that they can be re- > > > enabled. > > > = > > > Changes since v1: > > > =A0- PMD entry locking is now done based on the starting offset of > > > the PMD entry, rather than on the radix tree slot which was > > > unreliable. (Jan) > > > =A0- Fixed the one issue I could find with hole punch.=A0=A0As far as= I > > > can tell hole punch now works correctly for both PMD and PTE DAX > > > entries, 4k zero pages and huge zero pages. > > > =A0- Fixed the way that ext2 returns the size of holes in > > > ext2_get_block(). (Jan) > > > =A0- Made the 'wait_table' global variable static in respnse to a > > > sparse warning. > > > =A0- Fixed some more inconsitent usage between the names 'ret' and > > > 'entry' for radix tree entry variables. > > > = > > > Ross Zwisler (9): > > > =A0 ext4: allow DAX writeback for hole punch > > > =A0 ext2: tell DAX the size of allocation holes > > > =A0 ext4: tell DAX the size of allocation holes > > > =A0 dax: remove buffer_size_valid() > > > =A0 dax: make 'wait_table' global variable static > > > =A0 dax: consistent variable naming for DAX entries > > > =A0 dax: coordinate locking for offsets in PMD range > > > =A0 dax: re-enable DAX PMD support > > > =A0 dax: remove "depends on BROKEN" from FS_DAX_PMD > > > = > > > =A0fs/Kconfig=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0|=A0=A0=A01 - > > > =A0fs/dax.c=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0| 297 ++++++++++++++++= +++++++++++++----------- > > > ------------ > > > =A0fs/ext2/inode.c=A0=A0=A0=A0=A0|=A0=A0=A03 + > > > =A0fs/ext4/inode.c=A0=A0=A0=A0=A0|=A0=A0=A07 +- > > > =A0include/linux/dax.h |=A0=A029 ++++- > > > =A0mm/filemap.c=A0=A0=A0=A0=A0=A0=A0=A0|=A0=A0=A06 +- > > > =A06 files changed, 201 insertions(+), 142 deletions(-) > > > = > > > --=A0 > > > 2.9.0 > > = > > Ping on this series?=A0=A0Any objections or comments? > = > Hi Ross, > = > I am seeing a major performance loss in fio mmap test with this patch- > set applied. =A0This happens with or without my patches [1] applied on > top of yours. =A0Without my patches,=A0dax_pmd_fault() falls back to the > pte handler since an mmap'ed address is not 2MB-aligned. > = > I have attached three test results. > =A0o rc4.log - 4.8.0-rc4 (base) > =A0o non-pmd.log - 4.8.0-rc4 + your patchset (fall back to pte) > =A0o pmd.log - 4.8.0-rc4 + your patchset + my patchset (use pmd maps) > = > My test steps are as follows. > = > mkfs.ext4 -O bigalloc -C 2M /dev/pmem0 > mount -o dax /dev/pmem0 /mnt/pmem0 > numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio test.fio > = > "test.fio" > --- > [global] > bs=3D4k > size=3D2G > directory=3D/mnt/pmem0 > ioengine=3Dmmap > [randrw] > rw=3Drandrw > --- > = > Can you please take a look? Yep, thanks for the report. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754198AbcHaVgO (ORCPT ); Wed, 31 Aug 2016 17:36:14 -0400 Received: from mga04.intel.com ([192.55.52.120]:64225 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753708AbcHaVgM (ORCPT ); Wed, 31 Aug 2016 17:36:12 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,263,1470726000"; d="scan'208";a="1049846289" Date: Wed, 31 Aug 2016 15:36:07 -0600 From: Ross Zwisler To: "Kani, Toshimitsu" Cc: "ross.zwisler@linux.intel.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "adilger.kernel@dilger.ca" , "viro@zeniv.linux.org.uk" , "dan.j.williams@intel.com" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "jack@suse.com" , "tytso@mit.edu" , "linux-ext4@vger.kernel.org" , "david@fromorbit.com" Subject: Re: [PATCH v2 0/9] re-enable DAX PMD support Message-ID: <20160831213607.GA6921@linux.intel.com> Mail-Followup-To: Ross Zwisler , "Kani, Toshimitsu" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "adilger.kernel@dilger.ca" , "viro@zeniv.linux.org.uk" , "dan.j.williams@intel.com" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "jack@suse.com" , "tytso@mit.edu" , "linux-ext4@vger.kernel.org" , "david@fromorbit.com" References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160830230150.GA12173@linux.intel.com> <1472674799.2092.19.camel@hpe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1472674799.2092.19.camel@hpe.com> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 31, 2016 at 08:20:48PM +0000, Kani, Toshimitsu wrote: > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote: > > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > > > > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix > > > tree based locking.  This series allows DAX PMDs to participate in > > > the DAX radix tree based locking scheme so that they can be re- > > > enabled. > > > > > > Changes since v1: > > >  - PMD entry locking is now done based on the starting offset of > > > the PMD entry, rather than on the radix tree slot which was > > > unreliable. (Jan) > > >  - Fixed the one issue I could find with hole punch.  As far as I > > > can tell hole punch now works correctly for both PMD and PTE DAX > > > entries, 4k zero pages and huge zero pages. > > >  - Fixed the way that ext2 returns the size of holes in > > > ext2_get_block(). (Jan) > > >  - Made the 'wait_table' global variable static in respnse to a > > > sparse warning. > > >  - Fixed some more inconsitent usage between the names 'ret' and > > > 'entry' for radix tree entry variables. > > > > > > Ross Zwisler (9): > > >   ext4: allow DAX writeback for hole punch > > >   ext2: tell DAX the size of allocation holes > > >   ext4: tell DAX the size of allocation holes > > >   dax: remove buffer_size_valid() > > >   dax: make 'wait_table' global variable static > > >   dax: consistent variable naming for DAX entries > > >   dax: coordinate locking for offsets in PMD range > > >   dax: re-enable DAX PMD support > > >   dax: remove "depends on BROKEN" from FS_DAX_PMD > > > > > >  fs/Kconfig          |   1 - > > >  fs/dax.c            | 297 +++++++++++++++++++++++++++++----------- > > > ------------ > > >  fs/ext2/inode.c     |   3 + > > >  fs/ext4/inode.c     |   7 +- > > >  include/linux/dax.h |  29 ++++- > > >  mm/filemap.c        |   6 +- > > >  6 files changed, 201 insertions(+), 142 deletions(-) > > > > > > --  > > > 2.9.0 > > > > Ping on this series?  Any objections or comments? > > Hi Ross, > > I am seeing a major performance loss in fio mmap test with this patch- > set applied.  This happens with or without my patches [1] applied on > top of yours.  Without my patches, dax_pmd_fault() falls back to the > pte handler since an mmap'ed address is not 2MB-aligned. > > I have attached three test results. >  o rc4.log - 4.8.0-rc4 (base) >  o non-pmd.log - 4.8.0-rc4 + your patchset (fall back to pte) >  o pmd.log - 4.8.0-rc4 + your patchset + my patchset (use pmd maps) > > My test steps are as follows. > > mkfs.ext4 -O bigalloc -C 2M /dev/pmem0 > mount -o dax /dev/pmem0 /mnt/pmem0 > numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio test.fio > > "test.fio" > --- > [global] > bs=4k > size=2G > directory=/mnt/pmem0 > ioengine=mmap > [randrw] > rw=randrw > --- > > Can you please take a look? Yep, thanks for the report. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 31 Aug 2016 15:36:07 -0600 From: Ross Zwisler To: "Kani, Toshimitsu" Cc: "ross.zwisler@linux.intel.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "adilger.kernel@dilger.ca" , "viro@zeniv.linux.org.uk" , "dan.j.williams@intel.com" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "jack@suse.com" , "tytso@mit.edu" , "linux-ext4@vger.kernel.org" , "david@fromorbit.com" Subject: Re: [PATCH v2 0/9] re-enable DAX PMD support Message-ID: <20160831213607.GA6921@linux.intel.com> References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160830230150.GA12173@linux.intel.com> <1472674799.2092.19.camel@hpe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1472674799.2092.19.camel@hpe.com> Sender: owner-linux-mm@kvack.org List-ID: On Wed, Aug 31, 2016 at 08:20:48PM +0000, Kani, Toshimitsu wrote: > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote: > > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > > > > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix > > > tree based locking.��This series allows DAX PMDs to participate in > > > the DAX radix tree based locking scheme so that they can be re- > > > enabled. > > > > > > Changes since v1: > > > �- PMD entry locking is now done based on the starting offset of > > > the PMD entry, rather than on the radix tree slot which was > > > unreliable. (Jan) > > > �- Fixed the one issue I could find with hole punch.��As far as I > > > can tell hole punch now works correctly for both PMD and PTE DAX > > > entries, 4k zero pages and huge zero pages. > > > �- Fixed the way that ext2 returns the size of holes in > > > ext2_get_block(). (Jan) > > > �- Made the 'wait_table' global variable static in respnse to a > > > sparse warning. > > > �- Fixed some more inconsitent usage between the names 'ret' and > > > 'entry' for radix tree entry variables. > > > > > > Ross Zwisler (9): > > > � ext4: allow DAX writeback for hole punch > > > � ext2: tell DAX the size of allocation holes > > > � ext4: tell DAX the size of allocation holes > > > � dax: remove buffer_size_valid() > > > � dax: make 'wait_table' global variable static > > > � dax: consistent variable naming for DAX entries > > > � dax: coordinate locking for offsets in PMD range > > > � dax: re-enable DAX PMD support > > > � dax: remove "depends on BROKEN" from FS_DAX_PMD > > > > > > �fs/Kconfig����������|���1 - > > > �fs/dax.c������������| 297 +++++++++++++++++++++++++++++----------- > > > ------------ > > > �fs/ext2/inode.c�����|���3 + > > > �fs/ext4/inode.c�����|���7 +- > > > �include/linux/dax.h |��29 ++++- > > > �mm/filemap.c��������|���6 +- > > > �6 files changed, 201 insertions(+), 142 deletions(-) > > > > > > --� > > > 2.9.0 > > > > Ping on this series?��Any objections or comments? > > Hi Ross, > > I am seeing a major performance loss in fio mmap test with this patch- > set applied. �This happens with or without my patches [1] applied on > top of yours. �Without my patches,�dax_pmd_fault() falls back to the > pte handler since an mmap'ed address is not 2MB-aligned. > > I have attached three test results. > �o rc4.log - 4.8.0-rc4 (base) > �o non-pmd.log - 4.8.0-rc4 + your patchset (fall back to pte) > �o pmd.log - 4.8.0-rc4 + your patchset + my patchset (use pmd maps) > > My test steps are as follows. > > mkfs.ext4 -O bigalloc -C 2M /dev/pmem0 > mount -o dax /dev/pmem0 /mnt/pmem0 > numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio test.fio > > "test.fio" > --- > [global] > bs=4k > size=2G > directory=/mnt/pmem0 > ioengine=mmap > [randrw] > rw=randrw > --- > > Can you please take a look? Yep, thanks for the report. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ross Zwisler Subject: Re: [PATCH v2 0/9] re-enable DAX PMD support Date: Wed, 31 Aug 2016 15:36:07 -0600 Message-ID: <20160831213607.GA6921@linux.intel.com> References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160830230150.GA12173@linux.intel.com> <1472674799.2092.19.camel@hpe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: "tytso-3s7WtUTddSA@public.gmane.org" , "akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org" , "mawilcox-0li6OtcxBFHby3iVrkZq2A@public.gmane.org" , "linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org" , "david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org" , "adilger.kernel-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org" , "viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org" , "jack-IBi9RG/b67k@public.gmane.org" , "linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: "Kani, Toshimitsu" Return-path: Content-Disposition: inline In-Reply-To: <1472674799.2092.19.camel-ZPxbGqLxI0U@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" List-Id: linux-ext4.vger.kernel.org On Wed, Aug 31, 2016 at 08:20:48PM +0000, Kani, Toshimitsu wrote: > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote: > > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > > > = > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix > > > tree based locking.=A0=A0This series allows DAX PMDs to participate in > > > the DAX radix tree based locking scheme so that they can be re- > > > enabled. > > > = > > > Changes since v1: > > > =A0- PMD entry locking is now done based on the starting offset of > > > the PMD entry, rather than on the radix tree slot which was > > > unreliable. (Jan) > > > =A0- Fixed the one issue I could find with hole punch.=A0=A0As far as= I > > > can tell hole punch now works correctly for both PMD and PTE DAX > > > entries, 4k zero pages and huge zero pages. > > > =A0- Fixed the way that ext2 returns the size of holes in > > > ext2_get_block(). (Jan) > > > =A0- Made the 'wait_table' global variable static in respnse to a > > > sparse warning. > > > =A0- Fixed some more inconsitent usage between the names 'ret' and > > > 'entry' for radix tree entry variables. > > > = > > > Ross Zwisler (9): > > > =A0 ext4: allow DAX writeback for hole punch > > > =A0 ext2: tell DAX the size of allocation holes > > > =A0 ext4: tell DAX the size of allocation holes > > > =A0 dax: remove buffer_size_valid() > > > =A0 dax: make 'wait_table' global variable static > > > =A0 dax: consistent variable naming for DAX entries > > > =A0 dax: coordinate locking for offsets in PMD range > > > =A0 dax: re-enable DAX PMD support > > > =A0 dax: remove "depends on BROKEN" from FS_DAX_PMD > > > = > > > =A0fs/Kconfig=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0|=A0=A0=A01 - > > > =A0fs/dax.c=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0| 297 ++++++++++++++++= +++++++++++++----------- > > > ------------ > > > =A0fs/ext2/inode.c=A0=A0=A0=A0=A0|=A0=A0=A03 + > > > =A0fs/ext4/inode.c=A0=A0=A0=A0=A0|=A0=A0=A07 +- > > > =A0include/linux/dax.h |=A0=A029 ++++- > > > =A0mm/filemap.c=A0=A0=A0=A0=A0=A0=A0=A0|=A0=A0=A06 +- > > > =A06 files changed, 201 insertions(+), 142 deletions(-) > > > = > > > --=A0 > > > 2.9.0 > > = > > Ping on this series?=A0=A0Any objections or comments? > = > Hi Ross, > = > I am seeing a major performance loss in fio mmap test with this patch- > set applied. =A0This happens with or without my patches [1] applied on > top of yours. =A0Without my patches,=A0dax_pmd_fault() falls back to the > pte handler since an mmap'ed address is not 2MB-aligned. > = > I have attached three test results. > =A0o rc4.log - 4.8.0-rc4 (base) > =A0o non-pmd.log - 4.8.0-rc4 + your patchset (fall back to pte) > =A0o pmd.log - 4.8.0-rc4 + your patchset + my patchset (use pmd maps) > = > My test steps are as follows. > = > mkfs.ext4 -O bigalloc -C 2M /dev/pmem0 > mount -o dax /dev/pmem0 /mnt/pmem0 > numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio test.fio > = > "test.fio" > --- > [global] > bs=3D4k > size=3D2G > directory=3D/mnt/pmem0 > ioengine=3Dmmap > [randrw] > rw=3Drandrw > --- > = > Can you please take a look? Yep, thanks for the report. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f198.google.com (mail-pf0-f198.google.com [209.85.192.198]) by kanga.kvack.org (Postfix) with ESMTP id 7281A82F64 for ; Wed, 31 Aug 2016 17:36:10 -0400 (EDT) Received: by mail-pf0-f198.google.com with SMTP id g202so11791980pfb.3 for ; Wed, 31 Aug 2016 14:36:10 -0700 (PDT) Received: from mga01.intel.com (mga01.intel.com. [192.55.52.88]) by mx.google.com with ESMTPS id b64si1687753pfa.51.2016.08.31.14.36.09 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 31 Aug 2016 14:36:09 -0700 (PDT) Date: Wed, 31 Aug 2016 15:36:07 -0600 From: Ross Zwisler Subject: Re: [PATCH v2 0/9] re-enable DAX PMD support Message-ID: <20160831213607.GA6921@linux.intel.com> References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160830230150.GA12173@linux.intel.com> <1472674799.2092.19.camel@hpe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1472674799.2092.19.camel@hpe.com> Sender: owner-linux-mm@kvack.org List-ID: To: "Kani, Toshimitsu" Cc: "ross.zwisler@linux.intel.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "adilger.kernel@dilger.ca" , "viro@zeniv.linux.org.uk" , "dan.j.williams@intel.com" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "jack@suse.com" , "tytso@mit.edu" , "linux-ext4@vger.kernel.org" , "david@fromorbit.com" On Wed, Aug 31, 2016 at 08:20:48PM +0000, Kani, Toshimitsu wrote: > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote: > > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > > > > > > DAX PMDs have been disabled since Jan Kara introduced DAX radix > > > tree based locking. This series allows DAX PMDs to participate in > > > the DAX radix tree based locking scheme so that they can be re- > > > enabled. > > > > > > Changes since v1: > > > - PMD entry locking is now done based on the starting offset of > > > the PMD entry, rather than on the radix tree slot which was > > > unreliable. (Jan) > > > - Fixed the one issue I could find with hole punch. As far as I > > > can tell hole punch now works correctly for both PMD and PTE DAX > > > entries, 4k zero pages and huge zero pages. > > > - Fixed the way that ext2 returns the size of holes in > > > ext2_get_block(). (Jan) > > > - Made the 'wait_table' global variable static in respnse to a > > > sparse warning. > > > - Fixed some more inconsitent usage between the names 'ret' and > > > 'entry' for radix tree entry variables. > > > > > > Ross Zwisler (9): > > > ext4: allow DAX writeback for hole punch > > > ext2: tell DAX the size of allocation holes > > > ext4: tell DAX the size of allocation holes > > > dax: remove buffer_size_valid() > > > dax: make 'wait_table' global variable static > > > dax: consistent variable naming for DAX entries > > > dax: coordinate locking for offsets in PMD range > > > dax: re-enable DAX PMD support > > > dax: remove "depends on BROKEN" from FS_DAX_PMD > > > > > > fs/Kconfig | 1 - > > > fs/dax.c | 297 +++++++++++++++++++++++++++++----------- > > > ------------ > > > fs/ext2/inode.c | 3 + > > > fs/ext4/inode.c | 7 +- > > > include/linux/dax.h | 29 ++++- > > > mm/filemap.c | 6 +- > > > 6 files changed, 201 insertions(+), 142 deletions(-) > > > > > > -- > > > 2.9.0 > > > > Ping on this series? Any objections or comments? > > Hi Ross, > > I am seeing a major performance loss in fio mmap test with this patch- > set applied. This happens with or without my patches [1] applied on > top of yours. Without my patches, dax_pmd_fault() falls back to the > pte handler since an mmap'ed address is not 2MB-aligned. > > I have attached three test results. > o rc4.log - 4.8.0-rc4 (base) > o non-pmd.log - 4.8.0-rc4 + your patchset (fall back to pte) > o pmd.log - 4.8.0-rc4 + your patchset + my patchset (use pmd maps) > > My test steps are as follows. > > mkfs.ext4 -O bigalloc -C 2M /dev/pmem0 > mount -o dax /dev/pmem0 /mnt/pmem0 > numactl --preferred block:pmem0 --cpunodebind block:pmem0 fio test.fio > > "test.fio" > --- > [global] > bs=4k > size=2G > directory=/mnt/pmem0 > ioengine=mmap > [randrw] > rw=randrw > --- > > Can you please take a look? Yep, thanks for the report. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org