From: Rik van Riel The NUMA placement code has been rewritten several times, but the basic ideas took a lot of work to develop. The people who put in the work deserve credit for it. Thanks Andrea & Peter :) [ The Documentation/scheduler/numa-problem.txt file should probably be rewritten once we figure out the final details of what the NUMA code needs to do, and why. ] Signed-off-by: Rik van Riel Acked-by: Peter Zijlstra Cc: aarcange@redhat.com Cc: Linus Torvalds Cc: Andrew Morton Signed-off-by: Ingo Molnar ---- This is against tip.git numa/core --- CREDITS | 1 + kernel/sched/fair.c | 3 +++ mm/memory.c | 2 ++ 3 files changed, 6 insertions(+) Index: tip/CREDITS =================================================================== --- tip.orig/CREDITS +++ tip/CREDITS @@ -125,6 +125,7 @@ D: Author of pscan that helps to fix lp/ D: Author of lil (Linux Interrupt Latency benchmark) D: Fixed the shm swap deallocation at swapoff time (try_to_unuse message) D: VM hacker +D: NUMA task placement D: Various other kernel hacks S: Imola 40026 S: Italy Index: tip/kernel/sched/fair.c =================================================================== --- tip.orig/kernel/sched/fair.c +++ tip/kernel/sched/fair.c @@ -18,6 +18,9 @@ * * Adaptive scheduling granularity, math enhancements by Peter Zijlstra * Copyright (C) 2007 Red Hat, Inc., Peter Zijlstra + * + * NUMA placement, statistics and algorithm by Andrea Arcangeli, + * CFS balancing changes by Peter Zijlstra. Copyright (C) 2012 Red Hat, Inc. */ #include Index: tip/mm/memory.c =================================================================== --- tip.orig/mm/memory.c +++ tip/mm/memory.c @@ -36,6 +36,8 @@ * (Gerhard.Wichert@pdb.siemens.de) * * Aug/Sep 2004 Changed to four level page tables (Andi Kleen) + * + * 2012 - NUMA placement page faults (Andrea Arcangeli, Peter Zijlstra) */ #include -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/