From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>
Cc: 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 v4 3/8] mm: Add support for PUD-sized transparent hugepages
Date: Tue, 29 Mar 2016 15:17:10 -0700 [thread overview]
Message-ID: <20160329151710.6a256611fd28637d5c40ac3c@linux-foundation.org> (raw)
In-Reply-To: <1454242175-16870-4-git-send-email-matthew.r.wilcox@intel.com>
On Sun, 31 Jan 2016 23:09:30 +1100 Matthew Wilcox <matthew.r.wilcox@intel.com> wrote:
> From: Matthew Wilcox <willy@linux.intel.com>
>
> The current transparent hugepage code only supports PMDs. This patch
> adds support for transparent use of PUDs with DAX. It does not include
> support for anonymous pages.
>
> Most of this patch simply parallels the work that was done for huge PMDs.
> The only major difference is how the new ->pud_entry method in mm_walk
> works. The ->pmd_entry method replaces the ->pte_entry method, whereas
> the ->pud_entry method works along with either ->pmd_entry or ->pte_entry.
> The pagewalk code takes care of locking the PUD before calling ->pud_walk,
> so handlers do not need to worry whether the PUD is stable.
Why is this patchset always so hard to compile :(
> ...
>
> --- a/include/linux/pfn_t.h
> +++ b/include/linux/pfn_t.h
> @@ -82,6 +82,13 @@ static inline pmd_t pfn_t_pmd(pfn_t pfn, pgprot_t pgprot)
> {
> return pfn_pmd(pfn_t_to_pfn(pfn), pgprot);
> }
> +
> +#ifdef CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
> +static inline pud_t pfn_t_pud(pfn_t pfn, pgprot_t pgprot)
> +{
> + return pfn_pud(pfn_t_to_pfn(pfn), pgprot);
> +}
> +#endif
> #endif
>
> #ifdef __HAVE_ARCH_PTE_DEVMAP
> @@ -98,5 +105,6 @@ static inline bool pfn_t_devmap(pfn_t pfn)
> }
> pte_t pte_mkdevmap(pte_t pte);
> pmd_t pmd_mkdevmap(pmd_t pmd);
> +pud_t pud_mkdevmap(pud_t pud);
arm allnoconfig:
In file included from kernel/memremap.c:17:
include/linux/pfn_t.h:107: error: 'pud_mkdevmap' declared as function returning an array
because it expands to
pgd_t pud_mkdevmap(pgd_t pud);
and
typedef unsigned long pgd_t[2];
Also the patch provides no implementation of pud_mkdevmap() so it's
obviously going to break bisection.
--
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-03-29 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 12:09 [PATCH v4 0/8] Support for transparent PUD pages for DAX files Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 1/8] mm: Convert an open-coded VM_BUG_ON_VMA Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 2/8] mm,fs,dax: Change ->pmd_fault to ->huge_fault Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 3/8] mm: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-03-29 22:17 ` Andrew Morton [this message]
2016-03-30 14:05 ` Wilcox, Matthew R
2016-01-31 12:09 ` [PATCH v4 4/8] mincore: Add support for PUDs Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 5/8] procfs: Add support for PUDs to smaps, clear_refs and pagemap Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 6/8] x86: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 7/8] dax: Support for transparent PUD pages Matthew Wilcox
2016-01-31 12:09 ` [PATCH v4 8/8] ext4: 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=20160329151710.6a256611fd28637d5c40ac3c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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