Subject: + mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none.patch added to -mm tree
To: aneesh.kumar@xxxxxxxxxxxxxxxxxx,benh@xxxxxxxxxxxxxxxxxxx,mgorman@xxxxxxx,riel@xxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Wed, 08 Jan 2014 16:10:22 -0800
The patch titled
Subject: mm: move change_prot_numa outside CONFIG_ARCH_USES_NUMA_PROT_NONE
has been added to the -mm tree. Its filename is
mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
Subject: mm: move change_prot_numa outside CONFIG_ARCH_USES_NUMA_PROT_NONE
change_prot_numa should work even if _PAGE_NUMA != _PAGE_PROTNONE. On
archs like ppc64 that don't use _PAGE_PROTNONE and also have a separate
page table outside linux pagetable, we just need to make sure that when
calling change_prot_numa we flush the hardware page table entry so that
next page access result in a numa fault.
We still need to make sure we use the numa faulting logic only when
CONFIG_NUMA_BALANCING is set. This implies the migrate-on-fault (Lazy
migration) via mbind will only work if CONFIG_NUMA_BALANCING is set.
Previous discussion around the patch can be found at
http://article.gmane.org/gmane.linux.kernel.mm/109305
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
Reviewed-by: Rik van Riel <riel@xxxxxxxxxx>
Acked-by: Mel Gorman <mgorman@xxxxxxx>
Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/mm.h | 2 +-
mm/mempolicy.c | 5 ++---
2 files changed, 3 insertions(+), 4 deletions(-)
diff -puN include/linux/mm.h~mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none include/linux/mm.h
--- a/include/linux/mm.h~mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none
+++ a/include/linux/mm.h
@@ -1892,7 +1892,7 @@ static inline pgprot_t vm_get_page_prot(
}
#endif
-#ifdef CONFIG_ARCH_USES_NUMA_PROT_NONE
+#ifdef CONFIG_NUMA_BALANCING
unsigned long change_prot_numa(struct vm_area_struct *vma,
unsigned long start, unsigned long end);
#endif
diff -puN mm/mempolicy.c~mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none mm/mempolicy.c
--- a/mm/mempolicy.c~mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none
+++ a/mm/mempolicy.c
@@ -613,7 +613,7 @@ static inline int queue_pages_pgd_range(
return 0;
}
-#ifdef CONFIG_ARCH_USES_NUMA_PROT_NONE
+#ifdef CONFIG_NUMA_BALANCING
/*
* This is used to mark a range of virtual addresses to be inaccessible.
* These are later cleared by a NUMA hinting fault. Depending on these
@@ -627,7 +627,6 @@ unsigned long change_prot_numa(struct vm
unsigned long addr, unsigned long end)
{
int nr_updated;
- BUILD_BUG_ON(_PAGE_NUMA != _PAGE_PROTNONE);
nr_updated = change_protection(vma, addr, end, vma->vm_page_prot, 0, 1);
if (nr_updated)
@@ -641,7 +640,7 @@ static unsigned long change_prot_numa(st
{
return 0;
}
-#endif /* CONFIG_ARCH_USES_NUMA_PROT_NONE */
+#endif /* CONFIG_NUMA_BALANCING */
/*
* Walk through page tables and collect pages to be migrated.
_
Patches currently in -mm which might be from aneesh.kumar@xxxxxxxxxxxxxxxxxx are
mm-move-change_prot_numa-outside-config_arch_uses_numa_prot_none.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
