[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1528131620.7898.110.camel@surriel.com>
Date: Mon, 04 Jun 2018 13:00:20 -0400
From: Rik van Riel <riel@...riel.com>
To: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 09/19] sched/numa: Modify migrate_swap to accept
additional params
On Mon, 2018-06-04 at 15:30 +0530, Srikar Dronamraju wrote:
> There are checks in migrate_swap_stop that check if the task/cpu
> combination is as per migrate_swap_arg before migrating.
>
> However atleast one of the two tasks to be swapped by migrate_swap
> could
> have migrated to a completely different cpu before updating the
> migrate_swap_arg. The new cpu where the task is currently running
> could
> be a different node too. If the task has migrated, numa balancer
> might
> end up placing a task in a wrong node. Instead of achieving node
> consolidation, it may end up spreading the load across nodes.
>
> To avoid that pass the cpus as additional parameters.
>
> While here, place migrate_swap under CONFIG_NUMA_BALANCING.
>
> Signed-off-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Reviewed-by: Rik van Riel <riel@...riel.com>
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists