[PATCH 00/19] sched-numa rewrite

[Peter Zijlstra]

Hi all,

After having had a talk with Rik about all this NUMA nonsense where he proposed
the scheme implemented in the next to last patch, I came up with a related
means of doing the home-node selection.

I've also switched to (ab)using PROT_NONE for driving the migration faults.

These patches go on top of tip/master with origin/master (Linus' tree) merged in.

Since the posting of last week (which was private due to operator error and not
intention) Ingo dropped all the previous patches from tip and I did a complete
rebase of the series, making all the back and forth of old and new stuff go away.

---
 arch/x86/include/asm/pgtable.h |    1 +
 drivers/base/node.c            |    2 +-
 include/linux/huge_mm.h        |    3 +
 include/linux/init_task.h      |    9 +
 include/linux/mempolicy.h      |   30 ++-
 include/linux/migrate.h        |    7 +
 include/linux/migrate_mode.h   |    3 +
 include/linux/mm.h             |   12 +
 include/linux/mm_types.h       |   12 +
 include/linux/mmzone.h         |    1 -
 include/linux/sched.h          |   30 ++-
 include/linux/task_work.h      |    7 -
 kernel/exit.c                  |    5 +-
 kernel/sched/core.c            |   71 ++++++-
 kernel/sched/debug.c           |    3 +
 kernel/sched/fair.c            |  501 ++++++++++++++++++++++++++++++++++++++--
 kernel/sched/features.h        |   10 +
 kernel/sched/sched.h           |   37 +++
 kernel/sysctl.c                |   13 +-
 mm/huge_memory.c               |  165 +++++++++-----
 mm/memory.c                    |  125 ++++++++++-
 mm/mempolicy.c                 |  296 ++++++++++++++++++------
 mm/migrate.c                   |   85 ++++++-
 mm/mprotect.c                  |   24 ++-
 mm/vmstat.c                    |    1 -
 25 files changed, 1257 insertions(+), 196 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/