[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162929388912.3619265.15749940956800275665.b4-ty@ellerman.id.au>
Date: Wed, 18 Aug 2021 23:38:09 +1000
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: paulus@...ba.org, benh@...nel.crashing.org, mpe@...erman.id.au,
Laurent Dufour <ldufour@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
nathanl@...ux.ibm.com
Subject: Re: [PATCH v2] ppc64/numa: consider the max numa node for migratable LPAR
On Tue, 11 May 2021 09:31:36 +0200, Laurent Dufour wrote:
> When a LPAR is migratable, we should consider the maximum possible NUMA
> node instead the number of NUMA node from the actual system.
>
> The DT property 'ibm,current-associativity-domains' is defining the maximum
> number of nodes the LPAR can see when running on that box. But if the LPAR
> is being migrated on another box, it may seen up to the nodes defined by
> 'ibm,max-associativity-domains'. So if a LPAR is migratable, that value
> should be used.
>
> [...]
Applied to powerpc/next.
[1/1] ppc64/numa: consider the max numa node for migratable LPAR
https://git.kernel.org/powerpc/c/9c7248bb8de31f51c693bfa6a6ea53b1c07e0fa8
cheers
Powered by blists - more mailing lists