sched/numa: Initialise numa_migrate_retry
authorMel Gorman <mgorman@techsingularity.net>
Fri, 20 May 2022 10:35:16 +0000 (11:35 +0100)
committerPeter Zijlstra <peterz@infradead.org>
Mon, 13 Jun 2022 08:29:59 +0000 (10:29 +0200)
commit70ce3ea9aa4ed901c8a90de667df5ef307766e71
treec44a8d0d33c9fd2bd4ffeba19c1c9008dda0cace
parentb13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3
sched/numa: Initialise numa_migrate_retry

On clone, numa_migrate_retry is inherited from the parent which means
that the first NUMA placement of a task is non-deterministic. This
affects when load balancing recognises numa tasks and whether to
migrate "regular", "remote" or "all" tasks between NUMA scheduler
domains.

Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
Link: https://lore.kernel.org/r/20220520103519.1863-2-mgorman@techsingularity.net
kernel/sched/fair.c