From: Balbir Singh <bsingharora@gmail.com>
To: Oliver O'Halloran <oohall@gmail.com>
Cc: "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 3/6] powerpc/vmemmap: Add altmap support
Date: Tue, 23 May 2017 19:25:15 +1000 [thread overview]
Message-ID: <CAKTCnzk+8zNDp-fYbrry_RDHfOAHgiB6r8EXScjemWqMuFkdPA@mail.gmail.com> (raw)
In-Reply-To: <20170523040524.13717-3-oohall@gmail.com>
On Tue, May 23, 2017 at 2:05 PM, Oliver O'Halloran <oohall@gmail.com> wrote:
> Adds support to powerpc for the altmap feature of ZONE_DEVICE memory. An
> altmap is a driver provided region that is used to provide the backing
> storage for the struct pages of ZONE_DEVICE memory. In situations where
> large amount of ZONE_DEVICE memory is being added to the system the
> altmap reduces pressure on main system memory by allowing the mm/
> metadata to be stored on the device itself rather in main memory.
>
> Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
> ---
> arch/powerpc/mm/init_64.c | 15 +++++++++++++--
> arch/powerpc/mm/mem.c | 16 +++++++++++++---
> 2 files changed, 26 insertions(+), 5 deletions(-)
>
> diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
> index 8851e4f5dbab..225fbb8034e6 100644
> --- a/arch/powerpc/mm/init_64.c
> +++ b/arch/powerpc/mm/init_64.c
> @@ -44,6 +44,7 @@
> #include <linux/slab.h>
> #include <linux/of_fdt.h>
> #include <linux/libfdt.h>
> +#include <linux/memremap.h>
>
> #include <asm/pgalloc.h>
> #include <asm/page.h>
> @@ -171,13 +172,17 @@ int __meminit vmemmap_populate(unsigned long start, unsigned long end, int node)
> pr_debug("vmemmap_populate %lx..%lx, node %d\n", start, end, node);
>
> for (; start < end; start += page_size) {
> + struct vmem_altmap *altmap;
> void *p;
> int rc;
>
> if (vmemmap_populated(start, page_size))
> continue;
>
> - p = vmemmap_alloc_block(page_size, node);
> + /* altmap lookups only work at section boundaries */
> + altmap = to_vmem_altmap(SECTION_ALIGN_DOWN(start));
> +
> + p = __vmemmap_alloc_block_buf(page_size, node, altmap);
> if (!p)
> return -ENOMEM;
>
> @@ -242,6 +247,8 @@ void __ref vmemmap_free(unsigned long start, unsigned long end)
>
> for (; start < end; start += page_size) {
> unsigned long nr_pages, addr;
> + struct vmem_altmap *altmap;
> + struct page *section_base;
> struct page *page;
>
> /*
> @@ -257,9 +264,13 @@ void __ref vmemmap_free(unsigned long start, unsigned long end)
> continue;
>
> page = pfn_to_page(addr >> PAGE_SHIFT);
> + section_base = pfn_to_page(vmemmap_section_start(start));
> nr_pages = 1 << page_order;
>
> - if (PageReserved(page)) {
> + altmap = to_vmem_altmap((unsigned long) section_base);
> + if (altmap) {
> + vmem_altmap_free(altmap, nr_pages);
> + } else if (PageReserved(page)) {
> /* allocated from bootmem */
> if (page_size < PAGE_SIZE) {
> /*
> diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
> index 9ee536ec0739..2c0c16f11eee 100644
> --- a/arch/powerpc/mm/mem.c
> +++ b/arch/powerpc/mm/mem.c
> @@ -36,6 +36,7 @@
> #include <linux/hugetlb.h>
> #include <linux/slab.h>
> #include <linux/vmalloc.h>
> +#include <linux/memremap.h>
>
> #include <asm/pgalloc.h>
> #include <asm/prom.h>
> @@ -159,11 +160,20 @@ int arch_remove_memory(u64 start, u64 size)
> {
> unsigned long start_pfn = start >> PAGE_SHIFT;
> unsigned long nr_pages = size >> PAGE_SHIFT;
> - struct zone *zone;
> + struct vmem_altmap *altmap;
> + struct page *page;
> int ret;
>
> - zone = page_zone(pfn_to_page(start_pfn));
> - ret = __remove_pages(zone, start_pfn, nr_pages);
> + /*
> + * If we have an altmap then we need to skip over any reserved PFNs
> + * when querying the zone.
> + */
> + page = pfn_to_page(start_pfn);
> + altmap = to_vmem_altmap((unsigned long) page);
> + if (altmap)
> + page += vmem_altmap_offset(altmap);
> +
> + ret = __remove_pages(page_zone(page), start_pfn, nr_pages);
> if (ret)
> return ret;
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
Balbir
--
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:[~2017-05-23 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 4:05 [PATCH 1/6] powerpc/mm: Wire up hpte_removebolted for powernv Oliver O'Halloran
2017-05-23 4:05 ` [PATCH 2/6] powerpc/vmemmap: Reshuffle vmemmap_free() Oliver O'Halloran
2017-05-23 4:05 ` [PATCH 3/6] powerpc/vmemmap: Add altmap support Oliver O'Halloran
2017-05-23 9:25 ` Balbir Singh [this message]
2017-05-23 4:05 ` [PATCH 4/6] powerpc/mm: Add devmap support for ppc64 Oliver O'Halloran
2017-05-23 4:23 ` Aneesh Kumar K.V
2017-05-23 6:42 ` Oliver O'Halloran
2017-05-23 10:40 ` Balbir Singh
2017-05-24 2:17 ` Oliver O'Halloran
2017-05-23 4:05 ` [PATCH 5/6] mm, x86: Add ARCH_HAS_ZONE_DEVICE Oliver O'Halloran
2017-05-23 6:42 ` Ingo Molnar
2017-05-23 9:20 ` Balbir Singh
2017-05-23 4:05 ` [PATCH 6/6] powerpc/mm: Enable ZONE_DEVICE on powerpc Oliver O'Halloran
2017-05-23 9:21 ` Balbir Singh
2017-05-23 9:27 ` [PATCH 1/6] powerpc/mm: Wire up hpte_removebolted for powernv Balbir Singh
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=CAKTCnzk+8zNDp-fYbrry_RDHfOAHgiB6r8EXScjemWqMuFkdPA@mail.gmail.com \
--to=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.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