[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20150819231414.BF91C140771@ozlabs.org>
Date: Thu, 20 Aug 2015 09:14:14 +1000 (AEST)
From: Michael Ellerman <mpe@...erman.id.au>
To: Nikunj A Dadhania <nikunj@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org
Cc: anton@...ba.org, linux-kernel@...r.kernel.org,
nikunj@...ux.vnet.ibm.com, bharata@...ux.vnet.ibm.com
Subject: Re: [RESEND] powerpc/numa: initialize distance lookup table from drconf path
On Thu, 2015-02-07 at 05:39:01 UTC, Nikunj A Dadhania wrote:
> In some situations, a NUMA guest that supports
> ibm,dynamic-memory-reconfiguration node will end up having flat NUMA
> distances between nodes. This is because of two problems in the
> current code.
>
> 1) Different representations of associativity lists.
>
> There is an assumption about the associativity list in
> initialize_distance_lookup_table(). Associativity list has two forms:
>
> a) [cpu,memory]@x/ibm,associativity has following
> format:
> <N> <N integers>
>
> b) ibm,dynamic-reconfiguration-memory/ibm,associativity-lookup-arrays
>
> <M> <N> <M associativity lists each having N integers>
> M = the number of associativity lists
> N = the number of entries per associativity list
>
> Fix initialize_distance_lookup_table() so that it does not assume
> "case a". And update the caller to skip the length field before
> sending the associativity list.
>
> 2) Distance table not getting updated from drconf path.
>
> Node distance table will not get initialized in certain cases as
> ibm,dynamic-reconfiguration-memory path does not initialize the
> lookup table.
>
> Call initialize_distance_lookup_table() from drconf path with
> appropriate associativity list.
>
> Reported-by: Bharata B Rao <bharata@...ux.vnet.ibm.com>
> Signed-off-by: Nikunj A Dadhania <nikunj@...ux.vnet.ibm.com>
> Acked-by: Anton Blanchard <anton@...ba.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1d805440a364b4a68562
cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists