SPARC and UltraSPARC platform development
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid.aziz@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: Fix numa node distance initialization
Date: Tue, 05 Jan 2016 21:02:25 +0000	[thread overview]
Message-ID: <568C2F61.3060107@oracle.com> (raw)
In-Reply-To: <1451986811-197131-1-git-send-email-nitin.m.gupta@oracle.com>

On 01/05/2016 02:40 AM, Nitin Gupta wrote:
> Orabug: 22495713
>
> Currently, NUMA node distance matrix is initialized only
> when a machine descriptor (MD) exists. However, sun4u
> machines (e.g. Sun Blade 2500) do not have an MD and thus
> distance values were left uninitialized. The initialization
> is now moved such that it happens on both sun4u and sun4v.
>
> Signed-off-by: Nitin Gupta <nitin.m.gupta@oracle.com>
> Tested-by: Mikael Pettersson <mikpelinux@gmail.com>
> ---
>   arch/sparc/mm/init_64.c | 15 ++++++++-------
>   1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
> index 3025bd5..ff63db5 100644
> --- a/arch/sparc/mm/init_64.c
> +++ b/arch/sparc/mm/init_64.c
> @@ -1267,13 +1267,6 @@ static int __init numa_parse_mdesc(void)
>   	int i, j, err, count;
>   	u64 node;
>
> -	/* Some sane defaults for numa latency values */
> -	for (i = 0; i < MAX_NUMNODES; i++) {
> -		for (j = 0; j < MAX_NUMNODES; j++)
> -			numa_latency[i][j] = (i = j) ?
> -				LOCAL_DISTANCE : REMOTE_DISTANCE;
> -	}
> -
>   	node = mdesc_node_by_name(md, MDESC_NODE_NULL, "latency-groups");
>   	if (node = MDESC_NODE_NULL) {
>   		mdesc_release(md);
> @@ -1374,6 +1367,14 @@ static int __init bootmem_init_numa(void)
>   	numadbg("bootmem_init_numa()\n");
>
>   	if (numa_enabled) {
> +		int i, j;
> +		/* Some sane defaults for numa latency values */
> +		for (i = 0; i < MAX_NUMNODES; i++) {
> +			for (j = 0; j < MAX_NUMNODES; j++)
> +				numa_latency[i][j] = (i = j) ?
> +					LOCAL_DISTANCE : REMOTE_DISTANCE;
> +		}
> +
>   		if (tlb_type = hypervisor)
>   			err = numa_parse_mdesc();
>   		else
>

If one were to boot up with "numa=off" kernel option, numa_latency array 
wouldn't be initialized by this code which will cause node_distance() to 
return 0 for any two nodes. Would it make more sense to do this 
initialization outside of "if (numa_enabled)" or is a value of 0, 
instead of LOCAL_DISTANCE when numa is not enabled, for node_distance() 
not a problem?

--
Khalid

  reply	other threads:[~2016-01-05 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  9:40 [PATCH] sparc64: Fix numa node distance initialization Nitin Gupta
2016-01-05 21:02 ` Khalid Aziz [this message]
2016-01-05 21:44 ` David Miller
2016-01-06  6:26 ` Nitin Gupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=568C2F61.3060107@oracle.com \
    --to=khalid.aziz@oracle.com \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox