From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753294AbcAVL0d (ORCPT ); Fri, 22 Jan 2016 06:26:33 -0500 Received: from ipmail06.adl2.internode.on.net ([150.101.137.129]:18476 "EHLO ipmail06.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752561AbcAVL0X (ORCPT ); Fri, 22 Jan 2016 06:26:23 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CXDwDjEKJWPGwtLHleKAECgw+BP4ZfgXieTwaLXIVChAOGCQICAQECgUVNAQEBAQEBBwEBAQFBP4RBAQEBBCcTHCMQCAMVAwklDwUlAwcaE4gavjsBAQEBBgIBHRiFUoU1h3eBDwEElnaNTY8Cjj+EXCguhyMBAQE Date: Fri, 22 Jan 2016 22:26:19 +1100 From: Dave Chinner To: "Darrick J. Wong" Cc: Matthew Wilcox , Andrew Morton , Matthew Wilcox , linux-mm@kvack.org, linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org Subject: Re: [PATCH v3 0/8] Support for transparent PUD pages for DAX files Message-ID: <20160122112619.GC6033@dastard> References: <1452282592-27290-1-git-send-email-matthew.r.wilcox@intel.com> <20160115194150.GA5751@birch.djwong.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160115194150.GA5751@birch.djwong.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 15, 2016 at 11:41:50AM -0800, Darrick J. Wong wrote: > On Fri, Jan 08, 2016 at 02:49:44PM -0500, Matthew Wilcox wrote: > > From: Matthew Wilcox > > > > Andrew, I think this is ready for a spin in -mm. > > > > v3: Rebased against current mmtom > > v2: Reduced churn in filesystems by switching to ->huge_fault interface > > Addressed concerns from Kirill > > > > We have customer demand to use 1GB pages to map DAX files. Unlike the 2MB > > page support, the Linux MM does not currently support PUD pages, so I have > > attempted to add support for the necessary pieces for DAX huge PUD pages. > > > > Filesystems still need work to allocate 1GB pages. With ext4, I can > > only get 16MB of contiguous space, although it is aligned. With XFS, > > I can get 80MB less than 1GB, and it's not aligned. The XFS problem > > may be due to the small amount of RAM in my test machine. > > "It's not aligned"... I don't know the details of what you're trying to do, but > are you trying to create a file where each GB of logical address space maps to > a contiguous GB of physical space, and both logical and physical offsets align > to a 1GB boundary? > > If the XFS is formatted with stripe unit/width of 1G, an extent size hint of 1G > is put on the file, and the whole file is allocated in 1G chunks, I think > you're supposed to be able to make the above happen: If you really, really want to guarantee 1GB aligned extents for file data on XFS, use the realtime device with a 1GB extent size..... Cheers, Dave. -- Dave Chinner david@fromorbit.com