|| ||Andi Kleen <email@example.com> |
|| ||firstname.lastname@example.org |
|| ||Fix NUMA problems in transparent hugepages v2 |
|| ||Tue, 22 Feb 2011 17:51:54 -0800|
|| ||email@example.com, firstname.lastname@example.org|
|| ||Article, Thread
v2: I dropped the controversal KSM changes and fixed
the interleaving bug. Now it's purely for transparent huge pages.
The current transparent hugepages daemon can mess up local
memory affinity on NUMA systems. When it copies memory to a
huge page it does not necessarily keep it on the same
node as the local allocations.
While fixing this I also found some more related issues:
- The NUMA policy interleaving for THP was using the small
page size, not the large parse size.
- THP copies also did not preserve the local node
- The accounting for local/remote allocations in the daemon
- There were no VM statistics counters for THP, which made it
impossible to analyze.
At least some of the bug fixes are 2.6.38 candidates IMHO
because some of the NUMA problems are pretty bad. In some workloads
this can cause performance problems.
What can be delayed are GFP_OTHERNODE and the statistics changes.
Andi Kleen (8):
Fix interleaving for transparent hugepages v2
Change alloc_pages_vma to pass down the policy node for local policy
Preserve original node for transparent huge page copies
Use correct numa policy node for transparent hugepages
Add __GFP_OTHER_NODE flag
Use GFP_OTHER_NODE for transparent huge pages
Add VM counters for transparent hugepages
include/linux/gfp.h | 13 ++++++++---
include/linux/vmstat.h | 11 ++++++++-
mm/huge_memory.c | 49 +++++++++++++++++++++++++++++++++--------------
mm/mempolicy.c | 16 +++++++-------
mm/page_alloc.c | 2 +-
mm/vmstat.c | 17 ++++++++++++++-
6 files changed, 76 insertions(+), 32 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/