linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 2/6] powerpc/pseries: rename distance_ref_points_depth to max_associativity_domain_index
Date: Thu, 22 Jul 2021 11:19:12 +1000	[thread overview]
Message-ID: <YPjHkKkrTOT31qsE@yekko> (raw)
In-Reply-To: <YPjC3W9BFbD+wMZz@yekko>

[-- Attachment #1: Type: text/plain, Size: 4789 bytes --]

On Thu, Jul 22, 2021 at 10:59:09AM +1000, David Gibson wrote:
> On Mon, Jun 28, 2021 at 08:41:13PM +0530, Aneesh Kumar K.V wrote:
> > No functional change in this patch
> > 
> > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
> 
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

No... wait, I take that back.  This change makes the code *more*
confusing.

"distance_ref_points_depth" is accurate - it's the length of the
distance_ref_points array.

"max_associativity_domain_index" is not.  That implies it's the
maximum value that a domain index can have - which it isn't.  You
could have 15 entries in every associativity array, but if only 2 of
them are referenced in distance_ref_points, then
"max_associativity_domain_index" would only be 2.

> 
> > ---
> >  arch/powerpc/mm/numa.c | 20 ++++++++++----------
> >  1 file changed, 10 insertions(+), 10 deletions(-)
> > 
> > diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
> > index 8365b298ec48..132813dd1a6c 100644
> > --- a/arch/powerpc/mm/numa.c
> > +++ b/arch/powerpc/mm/numa.c
> > @@ -56,7 +56,7 @@ static int n_mem_addr_cells, n_mem_size_cells;
> >  static int form1_affinity;
> >  
> >  #define MAX_DISTANCE_REF_POINTS 4
> > -static int distance_ref_points_depth;
> > +static int max_associativity_domain_index;
> >  static const __be32 *distance_ref_points;
> >  static int distance_lookup_table[MAX_NUMNODES][MAX_DISTANCE_REF_POINTS];
> >  
> > @@ -169,7 +169,7 @@ int cpu_distance(__be32 *cpu1_assoc, __be32 *cpu2_assoc)
> >  
> >  	int i, index;
> >  
> > -	for (i = 0; i < distance_ref_points_depth; i++) {
> > +	for (i = 0; i < max_associativity_domain_index; i++) {
> >  		index = be32_to_cpu(distance_ref_points[i]);
> >  		if (cpu1_assoc[index] == cpu2_assoc[index])
> >  			break;
> > @@ -193,7 +193,7 @@ int __node_distance(int a, int b)
> >  	if (!form1_affinity)
> >  		return ((a == b) ? LOCAL_DISTANCE : REMOTE_DISTANCE);
> >  
> > -	for (i = 0; i < distance_ref_points_depth; i++) {
> > +	for (i = 0; i < max_associativity_domain_index; i++) {
> >  		if (distance_lookup_table[a][i] == distance_lookup_table[b][i])
> >  			break;
> >  
> > @@ -213,7 +213,7 @@ static void initialize_distance_lookup_table(int nid,
> >  	if (!form1_affinity)
> >  		return;
> >  
> > -	for (i = 0; i < distance_ref_points_depth; i++) {
> > +	for (i = 0; i < max_associativity_domain_index; i++) {
> >  		const __be32 *entry;
> >  
> >  		entry = &associativity[be32_to_cpu(distance_ref_points[i]) - 1];
> > @@ -240,7 +240,7 @@ static int associativity_to_nid(const __be32 *associativity)
> >  		nid = NUMA_NO_NODE;
> >  
> >  	if (nid > 0 &&
> > -		of_read_number(associativity, 1) >= distance_ref_points_depth) {
> > +		of_read_number(associativity, 1) >= max_associativity_domain_index) {
> >  		/*
> >  		 * Skip the length field and send start of associativity array
> >  		 */
> > @@ -310,14 +310,14 @@ static int __init find_primary_domain_index(void)
> >  	 */
> >  	distance_ref_points = of_get_property(root,
> >  					"ibm,associativity-reference-points",
> > -					&distance_ref_points_depth);
> > +					&max_associativity_domain_index);
> >  
> >  	if (!distance_ref_points) {
> >  		dbg("NUMA: ibm,associativity-reference-points not found.\n");
> >  		goto err;
> >  	}
> >  
> > -	distance_ref_points_depth /= sizeof(int);
> > +	max_associativity_domain_index /= sizeof(int);
> >  
> >  	if (firmware_has_feature(FW_FEATURE_OPAL) ||
> >  	    firmware_has_feature(FW_FEATURE_TYPE1_AFFINITY)) {
> > @@ -328,7 +328,7 @@ static int __init find_primary_domain_index(void)
> >  	if (form1_affinity) {
> >  		index = of_read_number(distance_ref_points, 1);
> >  	} else {
> > -		if (distance_ref_points_depth < 2) {
> > +		if (max_associativity_domain_index < 2) {
> >  			printk(KERN_WARNING "NUMA: "
> >  				"short ibm,associativity-reference-points\n");
> >  			goto err;
> > @@ -341,10 +341,10 @@ static int __init find_primary_domain_index(void)
> >  	 * Warn and cap if the hardware supports more than
> >  	 * MAX_DISTANCE_REF_POINTS domains.
> >  	 */
> > -	if (distance_ref_points_depth > MAX_DISTANCE_REF_POINTS) {
> > +	if (max_associativity_domain_index > MAX_DISTANCE_REF_POINTS) {
> >  		printk(KERN_WARNING "NUMA: distance array capped at "
> >  			"%d entries\n", MAX_DISTANCE_REF_POINTS);
> > -		distance_ref_points_depth = MAX_DISTANCE_REF_POINTS;
> > +		max_associativity_domain_index = MAX_DISTANCE_REF_POINTS;
> >  	}
> >  
> >  	of_node_put(root);
> 



-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-07-22  2:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 15:11 [PATCH v5 0/6] Add support for FORM2 associativity Aneesh Kumar K.V
2021-06-28 15:11 ` [PATCH v5 1/6] powerpc/pseries: rename min_common_depth to primary_domain_index Aneesh Kumar K.V
2021-07-22  1:59   ` David Gibson
2021-07-22  2:36     ` David Gibson
2021-07-22  5:17       ` Aneesh Kumar K.V
2021-07-26  2:28         ` David Gibson
2021-06-28 15:11 ` [PATCH v5 2/6] powerpc/pseries: rename distance_ref_points_depth to max_associativity_domain_index Aneesh Kumar K.V
2021-07-22  0:59   ` David Gibson
2021-07-22  1:19     ` David Gibson [this message]
2021-06-28 15:11 ` [PATCH v5 3/6] powerpc/pseries: Rename TYPE1_AFFINITY to FORM1_AFFINITY Aneesh Kumar K.V
2021-06-28 15:11 ` [PATCH v5 4/6] powerpc/pseries: Consolidate different NUMA distance update code paths Aneesh Kumar K.V
2021-06-28 20:21   ` kernel test robot
2021-06-28 20:40   ` kernel test robot
2021-07-22  1:40   ` David Gibson
2021-07-22  7:07     ` Aneesh Kumar K.V
2021-07-26  2:37       ` David Gibson
2021-07-27  3:32         ` Aneesh Kumar K.V
2021-07-27  5:59           ` David Gibson
2021-06-28 15:11 ` [PATCH v5 5/6] powerpc/pseries: Add a helper for form1 cpu distance Aneesh Kumar K.V
2021-07-22  1:42   ` David Gibson
2021-07-22  7:09     ` Aneesh Kumar K.V
2021-07-26  2:38       ` David Gibson
2021-06-28 15:11 ` [PATCH v5 6/6] powerpc/pseries: Add support for FORM2 associativity Aneesh Kumar K.V
2021-07-22  2:28   ` David Gibson
2021-07-22  7:34     ` Aneesh Kumar K.V
2021-07-26  2:41       ` David Gibson
2021-07-13 14:27 ` [PATCH v5 0/6] " Daniel Henrique Barboza
2021-07-13 14:30   ` Aneesh Kumar K.V

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=YPjHkKkrTOT31qsE@yekko \
    --to=david@gibson.dropbear.id.au \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=danielhb413@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nathanl@linux.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).