diff options
| author |  Peter Zijlstra <peterz@infradead.org>
| 2013-10-07 11:28:52 +0100 |
|---|---|---|
| committer |  Ingo Molnar <mingo@kernel.org>
| 2013-10-09 12:40:09 +0200 |
| commit | 9e645ab6d089f5822479a833c6977c785bcfffe3 (patch) | |
| tree | 5f3de0a077588419e0a62e2eccd81c68a51c7de4 /kernel/fork.c | |
| parent | sched/numa: Mitigate chance that same task always updates PTEs (diff) | |
| download | linux-9e645ab6d089f5822479a833c6977c785bcfffe3.tar.gz linux-9e645ab6d089f5822479a833c6977c785bcfffe3.tar.bz2 linux-9e645ab6d089f5822479a833c6977c785bcfffe3.zip | |
sched/numa: Continue PTE scanning even if migrate rate limited
Avoiding marking PTEs pte_numa because a particular NUMA node is migrate rate
limited sees like a bad idea. Even if this node can't migrate anymore other
nodes might and we want up-to-date information to do balance decisions.
We already rate limit the actual migrations, this should leave enough
bandwidth to allow the non-migrating scanning. I think its important we
keep up-to-date information if we're going to do placement based on it.
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Mel Gorman <mgorman@suse.de>
Reviewed-by: Rik van Riel <riel@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Link: http://lkml.kernel.org/r/1381141781-10992-15-git-send-email-mgorman@suse.de
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions