I've been testing wider workloads and here's two more small and
obvious patches rounding up numa/core behavior around the edges.
The NUMA code should now be pretty unintrusive to all but the
long-running, memory-intense workloads where it's expected to
make a (positive) difference.
Short-run workloads like kbuild or hackbench don't trigger the
NUMA code now. The limits can be reconsidered later on,
iteratively - the goal now is to not regress.
Thanks,
Ingo
-------------->
Ingo Molnar (2):
sched: Exclude pinned tasks from the NUMA-balancing logic
sched: Add RSS filter to NUMA-balancing
include/linux/sched.h | 1 +
kernel/sched/core.c | 6 ++++++
kernel/sched/debug.c | 1 +
kernel/sched/fair.c | 53 +++++++++++++++++++++++++++++++++++++++++++++----
kernel/sched/features.h | 1 +
kernel/sysctl.c | 7 +++++++
6 files changed, 65 insertions(+), 4 deletions(-)
--
1.7.11.7
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
