linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <nathanl@linux.ibm.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v3 3/5] powerpc/numa: Use cpu node map of first sibling thread
Date: Wed, 11 Sep 2019 09:48:34 -0500	[thread overview]
Message-ID: <87lfuurirh.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190906135020.19772-4-srikar@linux.vnet.ibm.com>

Hi Srikar,

Srikar Dronamraju <srikar@linux.vnet.ibm.com> writes:
> @@ -467,15 +467,20 @@ static int of_drconf_to_nid_single(struct drmem_lmb *lmb)
>   */
>  static int numa_setup_cpu(unsigned long lcpu)
>  {
> -	int nid = NUMA_NO_NODE;
>  	struct device_node *cpu;
> +	int fcpu = cpu_first_thread_sibling(lcpu);
> +	int nid = NUMA_NO_NODE;
>  
>  	/*
>  	 * If a valid cpu-to-node mapping is already available, use it
>  	 * directly instead of querying the firmware, since it represents
>  	 * the most recent mapping notified to us by the platform (eg: VPHN).
> +	 * Since cpu_to_node binding remains the same for all threads in the
> +	 * core. If a valid cpu-to-node mapping is already available, for
> +	 * the first thread in the core, use it.
>  	 */
> -	if ((nid = numa_cpu_lookup_table[lcpu]) >= 0) {
> +	nid = numa_cpu_lookup_table[fcpu];
> +	if (nid >= 0) {
>  		map_cpu_to_node(lcpu, nid);
>  		return nid;
>  	}

Yes, we need to something like this to prevent a VPHN change that occurs
concurrently with onlining a core's threads from messing us up.

Is it a good assumption that the first thread of a sibling group will
have its mapping initialized first? I think the answer is yes for boot,
but hotplug... not so sure.


> @@ -496,6 +501,16 @@ static int numa_setup_cpu(unsigned long lcpu)
>  	if (nid < 0 || !node_possible(nid))
>  		nid = first_online_node;
>  
> +	/*
> +	 * Update for the first thread of the core. All threads of a core
> +	 * have to be part of the same node. This not only avoids querying
> +	 * for every other thread in the core, but always avoids a case
> +	 * where virtual node associativity change causes subsequent threads
> +	 * of a core to be associated with different nid.
> +	 */
> +	if (fcpu != lcpu)
> +		map_cpu_to_node(fcpu, nid);
> +

OK, I see that this somewhat addresses my concern above. But changing
this mapping for a remote cpu is unsafe except under specific
circumstances. I think this should first assert:

* numa_cpu_lookup_table[fcpu] == NUMA_NO_NODE
* cpu_online(fcpu) == false

to document and enforce the conditions that must hold for this to be OK.

  reply	other threads:[~2019-09-11 15:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 13:50 [PATCH v3 0/5] Early node associativity Srikar Dronamraju
2019-09-06 13:50 ` [PATCH v3 1/5] powerpc/vphn: Check for error from hcall_vphn Srikar Dronamraju
2019-09-06 13:50 ` [PATCH v3 2/5] powerpc/numa: Handle extra hcall_vphn error cases Srikar Dronamraju
2019-09-06 13:50 ` [PATCH v3 3/5] powerpc/numa: Use cpu node map of first sibling thread Srikar Dronamraju
2019-09-11 14:48   ` Nathan Lynch [this message]
2019-09-11 17:05     ` Srikar Dronamraju
2019-09-12 16:41       ` Nathan Lynch
2019-09-12 17:23         ` Srikar Dronamraju
2019-09-12 18:15           ` Nathan Lynch
2019-09-13  5:44             ` Srikar Dronamraju
2019-09-06 13:50 ` [PATCH v3 4/5] powerpc/numa: Early request for home node associativity Srikar Dronamraju
2019-09-06 13:50 ` [PATCH v3 5/5] powerpc/numa: Remove late " Srikar Dronamraju

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=87lfuurirh.fsf@linux.ibm.com \
    --to=nathanl@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=sathnaga@linux.vnet.ibm.com \
    --cc=srikar@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).