From: Matthew Wilcox <matthew.r.wilcox@intel.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Cc: Matthew Wilcox <willy@linux.intel.com>
Subject: [PATCH 00/10] Huge page support for DAX files
Date: Fri, 10 Jul 2015 16:29:15 -0400 [thread overview]
Message-ID: <1436560165-8943-1-git-send-email-matthew.r.wilcox@intel.com> (raw)
From: Matthew Wilcox <willy@linux.intel.com>
This series of patches adds support for using PMD page table entries
to map DAX files. We expect NV-DIMMs to start showing up that are
many gigabytes in size and the memory consumption of 4kB PTEs will
be astronomical.
The patch series leverages much of the Transparant Huge Pages
infrastructure, going so far as to borrow one of Kirill's patches from
his THP page cache series.
The ext2 and XFS patches are merely compile tested. The ext4 code has
survived the NVML test suite, some Trinity testing and an xfstests run.
Kirill A. Shutemov (1):
thp: vma_adjust_trans_huge(): adjust file-backed VMA too
Matthew Wilcox (9):
dax: Move DAX-related functions to a new header
thp: Prepare for DAX huge pages
mm: Add a pmd_fault handler
mm: Export various functions for the benefit of DAX
mm: Add vmf_insert_pfn_pmd()
dax: Add huge page fault support
ext2: Huge page fault support
ext4: Huge page fault support
xfs: Huge page fault support
Documentation/filesystems/dax.txt | 7 +-
fs/block_dev.c | 1 +
fs/dax.c | 152 ++++++++++++++++++++++++++++++++++++++
fs/ext2/file.c | 10 ++-
fs/ext2/inode.c | 1 +
fs/ext4/file.c | 11 ++-
fs/ext4/indirect.c | 1 +
fs/ext4/inode.c | 1 +
fs/xfs/xfs_buf.h | 1 +
fs/xfs/xfs_file.c | 30 +++++++-
fs/xfs/xfs_trace.h | 1 +
include/linux/dax.h | 39 ++++++++++
include/linux/fs.h | 14 ----
include/linux/huge_mm.h | 23 +++---
include/linux/mm.h | 2 +
mm/huge_memory.c | 100 ++++++++++++++++++-------
mm/memory.c | 30 ++++++--
17 files changed, 362 insertions(+), 62 deletions(-)
create mode 100644 include/linux/dax.h
--
2.1.4
--
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 reply other threads:[~2015-07-10 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 20:29 Matthew Wilcox [this message]
2015-07-10 20:29 ` [PATCH 01/10] thp: vma_adjust_trans_huge(): adjust file-backed VMA too Matthew Wilcox
2015-07-10 20:29 ` [PATCH 02/10] dax: Move DAX-related functions to a new header Matthew Wilcox
2015-07-10 20:29 ` [PATCH 03/10] thp: Prepare for DAX huge pages Matthew Wilcox
2015-07-19 11:03 ` Kirill A. Shutemov
2015-07-10 20:29 ` [PATCH 04/10] mm: Add a pmd_fault handler Matthew Wilcox
2015-07-10 20:29 ` [PATCH 05/10] mm: Export various functions for the benefit of DAX Matthew Wilcox
2015-07-10 20:29 ` [PATCH 06/10] mm: Add vmf_insert_pfn_pmd() Matthew Wilcox
2015-07-13 13:23 ` Jeff Moyer
2015-07-13 15:02 ` Matthew Wilcox
2015-07-10 20:29 ` [PATCH 07/10] dax: Add huge page fault support Matthew Wilcox
2015-07-13 15:05 ` Jan Kara
2015-07-13 15:33 ` Matthew Wilcox
2015-07-10 20:29 ` [PATCH 08/10] ext2: Huge " Matthew Wilcox
2015-07-10 20:29 ` [PATCH 09/10] ext4: " Matthew Wilcox
2015-07-10 20:29 ` [PATCH 10/10] xfs: " Matthew Wilcox
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=1436560165-8943-1-git-send-email-matthew.r.wilcox@intel.com \
--to=matthew.r.wilcox@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@linux.intel.com \
/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).