[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <019ceada-998c-8e5e-74fa-9606c922e096@arm.com>
Date: Thu, 19 Dec 2019 14:23:33 +0000
From: Valentin Schneider <valentin.schneider@....com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Mel Gorman <mgorman@...hsingularity.net>,
Vincent Guittot <vincent.guittot@...aro.org>,
Ingo Molnar <mingo@...nel.org>, pauld@...hat.com,
srikar@...ux.vnet.ibm.com, quentin.perret@....com,
dietmar.eggemann@....com, Morten.Rasmussen@....com,
hdanton@...a.com, parth@...ux.ibm.com, riel@...riel.com,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched, fair: Allow a small degree of load imbalance
between SD_NUMA domains
On 19/12/2019 11:46, Valentin Schneider wrote:
> As for picking values, right now we have
>
> 125 (default) / 117 (LLC domain) / 110 (SMT domain)
>
> We could have
>
> >> 2 (25%), >> 3 (12.5%), >> 4 (6.25%).
>
Hmph, I see that task_numa_migrate() starts with a slightly different value
(112), and does the same halving pattern as wake_affine_weight():
x = 100 + (sd->imbalance_pct - 100) / 2;
The 112 could use >> 3 (12.5%); the halving is just an extra shift with the
suggested changes.
> It's not strictly equivalent but IMO the whole imbalance_pct thing isn't
> very precise anyway; just needs to be good enough on a sufficient number of
> topologies.
>
>
>
>>> + env->imbalance = 0;
>>> +
>>> return;
>>> }
>>>
Powered by blists - more mailing lists