Re: [PATCH v3 0/4] Revisit NUMA imbalance tolerance and fork balancing

2020-11-20 Thread Mel Gorman
On Fri, Nov 20, 2020 at 01:58:11PM +0100, Peter Zijlstra wrote: > On Fri, Nov 20, 2020 at 09:06:26AM +, Mel Gorman wrote: > > > Mel Gorman (4): > > sched/numa: Rename nr_running and break out the magic number > > sched: Avoid unnecessary calculation of load imbalance at clone time > >

Re: [PATCH v3 0/4] Revisit NUMA imbalance tolerance and fork balancing

2020-11-20 Thread Peter Zijlstra
On Fri, Nov 20, 2020 at 09:06:26AM +, Mel Gorman wrote: > Mel Gorman (4): > sched/numa: Rename nr_running and break out the magic number > sched: Avoid unnecessary calculation of load imbalance at clone time > sched/numa: Allow a floating imbalance between NUMA nodes > sched: Limit

[PATCH v3 0/4] Revisit NUMA imbalance tolerance and fork balancing

2020-11-20 Thread Mel Gorman
Changelog since v2 o Build fix for !NUMA_BALANCING configurations Changelog since v1 o Split out patch that moves imbalance calculation o Strongly connect fork imbalance considerations with adjust_numa_imbalance When NUMA and CPU balancing were reconciled, there was an attempt to allow a degree