From: Dave Chinner <david@fromorbit.com>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
linux-mm@kvack.org, linux-nvdimm@lists.01.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 7/8] xfs: Support for transparent PUD pages
Date: Thu, 31 Dec 2015 10:30:27 +1100 [thread overview]
Message-ID: <20151230233007.GA6682@dastard> (raw)
In-Reply-To: <1450974037-24775-8-git-send-email-matthew.r.wilcox@intel.com>
On Thu, Dec 24, 2015 at 11:20:36AM -0500, Matthew Wilcox wrote:
> From: Matthew Wilcox <willy@linux.intel.com>
>
> Call into DAX to provide support for PUD pages, just like the PMD cases.
>
> Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> ---
> fs/xfs/xfs_file.c | 33 +++++++++++++++++++++++++++++++++
> fs/xfs/xfs_trace.h | 1 +
> 2 files changed, 34 insertions(+)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index f5392ab..a81b942 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -1600,6 +1600,38 @@ xfs_filemap_pmd_fault(
> return ret;
> }
>
> +STATIC int
> +xfs_filemap_pud_fault(
> + struct vm_area_struct *vma,
> + unsigned long addr,
> + pud_t *pud,
> + unsigned int flags)
> +{
> + struct inode *inode = file_inode(vma->vm_file);
> + struct xfs_inode *ip = XFS_I(inode);
> + int ret;
> +
> + if (!IS_DAX(inode))
> + return VM_FAULT_FALLBACK;
> +
> + trace_xfs_filemap_pud_fault(ip);
> +
> + if (flags & FAULT_FLAG_WRITE) {
> + sb_start_pagefault(inode->i_sb);
> + file_update_time(vma->vm_file);
> + }
> +
> + xfs_ilock(XFS_I(inode), XFS_MMAPLOCK_SHARED);
> + ret = __dax_pud_fault(vma, addr, pud, flags, xfs_get_blocks_dax_fault,
> + NULL);
> + xfs_iunlock(XFS_I(inode), XFS_MMAPLOCK_SHARED);
> +
> + if (flags & FAULT_FLAG_WRITE)
> + sb_end_pagefault(inode->i_sb);
> +
> + return ret;
> +}
> +
> /*
> * pfn_mkwrite was originally inteneded to ensure we capture time stamp
> * updates on write faults. In reality, it's need to serialise against
> @@ -1637,6 +1669,7 @@ xfs_filemap_pfn_mkwrite(
> static const struct vm_operations_struct xfs_file_vm_ops = {
> .fault = xfs_filemap_fault,
> .pmd_fault = xfs_filemap_pmd_fault,
> + .pud_fault = xfs_filemap_pud_fault,
This is getting silly - we now have 3 different page fault handlers
that all do exactly the same thing. Please abstract this so that the
page/pmd/pud is transparent and gets passed through to the generic
handler code that then handles the differences between page/pmd/pud
internally.
This, after all, is the original reason that the ->fault handler was
introduced....
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:[~2015-12-30 23:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 16:20 [PATCH 0/8] Support for transparent PUD pages Matthew Wilcox
2015-12-24 16:20 ` [PATCH 1/8] mm: Add optional support for PUD-sized transparent hugepages Matthew Wilcox
2015-12-28 10:05 ` Kirill A. Shutemov
2016-01-02 17:06 ` Matthew Wilcox
2016-01-04 20:30 ` Kirill A. Shutemov
2015-12-28 10:11 ` Kirill A. Shutemov
2015-12-24 16:20 ` [PATCH 2/8] mincore: Add support for PUDs Matthew Wilcox
2015-12-24 16:20 ` [PATCH 3/8] procfs: Add support for PUDs to smaps, clear_refs and pagemap Matthew Wilcox
2015-12-24 16:20 ` [PATCH 4/8] x86: Add support for PUD-sized transparent hugepages Matthew Wilcox
2015-12-24 16:20 ` [PATCH 5/8] dax: Support for transparent PUD pages Matthew Wilcox
2015-12-24 16:20 ` [PATCH 6/8] block_dev: Support PUD DAX mappings Matthew Wilcox
2015-12-24 16:20 ` [PATCH 7/8] xfs: Support for transparent PUD pages Matthew Wilcox
2015-12-30 23:30 ` Dave Chinner [this message]
2016-01-02 16:43 ` Matthew Wilcox
2016-01-03 20:33 ` Dave Chinner
2016-01-04 20:41 ` Kirill A. Shutemov
2016-01-04 22:01 ` Matthew Wilcox
2015-12-24 16:20 ` [PATCH 8/8] ext4: Transparent support for PUD-sized transparent huge pages 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=20151230233007.GA6682@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.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).