From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@linux.intel.com>,
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
Date: Fri, 22 Jan 2016 22:26:19 +1100 [thread overview]
Message-ID: <20160122112619.GC6033@dastard> (raw)
In-Reply-To: <20160115194150.GA5751@birch.djwong.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 <willy@linux.intel.com>
> >
> > 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
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-22 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 19:49 [PATCH v3 0/8] Support for transparent PUD pages for DAX files Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 1/8] mm: Convert an open-coded VM_BUG_ON_VMA Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 2/8] mm,fs,dax: Change ->pmd_fault to ->huge_fault Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 3/8] mm: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 4/8] mincore: Add support for PUDs Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 5/8] procfs: Add support for PUDs to smaps, clear_refs and pagemap Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 6/8] x86: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 7/8] dax: Support for transparent PUD pages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 8/8] ext4: Support for PUD-sized transparent huge pages Matthew Wilcox
2016-01-15 19:41 ` [PATCH v3 0/8] Support for transparent PUD pages for DAX files Darrick J. Wong
2016-01-22 11:26 ` Dave Chinner [this message]
2016-01-21 22:48 ` mingming cao
2016-01-22 14:11 ` Matthew Wilcox
2016-01-27 20:31 ` Andrew Morton
2016-01-27 20:39 ` Andrew Morton
2016-01-27 20:53 ` Wilcox, Matthew R
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=20160122112619.GC6033@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=willy@linux.intel.com \
--cc=x86@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).