On Fri, Apr 11, 2014 at 01:00:27PM -0400, r...@redhat.com wrote: > From: Rik van Riel <r...@redhat.com> > > The NUMA code is smart enough to distribute the memory of workloads > that span multiple NUMA nodes across those NUMA nodes. > > However, it still has a pretty high scan rate for such workloads, > because any memory that is left on a node other than the node of > the CPU that faulted on the memory is counted as non-local, which > causes the scan rate to go up. > > Counting the memory on any node where the task's numa group is > actively running as local, allows the scan rate to slow down > once the application is settled in. > > This should reduce the overhead of the automatic NUMA placement > code, when a workload spans multiple NUMA nodes. > > Signed-off-by: Rik van Riel <r...@redhat.com> > Tested-by: Vinod Chegu <chegu_vi...@hp.com>
Acked-by: Mel Gorman <mgor...@suse.de> -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
