On Wed, Aug 12, 2020 at 11:51:54AM +0800, ? wrote:
> OK. Thanks for your advice and I'll use label instead.
> In the case of migration failures, if there are still new failures after
> clearing (meaning the node is still overloaded), the scanning period would
> be doubled, just like not
Peter Zijlstra
> ; Juri Lelli ; Vincent
Guittot
> ; Dietmar Eggemann
> ; Steven Rostedt ;
> Ben Segall ; linux-kernel ker...@vger.kernel.org>; ??????
> Subject: Re: [RFC PATCH] sched/numa: fix bug in update_task_scan_period
>
> On Tue, Aug 11, 2020 at 04:30:
On Tue, Aug 11, 2020 at 04:30:31PM +0800, ? wrote:
> When p->numa_faults_locality[2] > 0, numa_scan_period is doubled, but
> this array will never be cleared, which causes scanning period always
> reaching its max value. This patch clears numa_faults_locality after
> numa_scan_period being
3 matches
Mail list logo
