public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] you have how many nodes??
Date: Tue, 21 Oct 2003 10:44:02 -0700	[thread overview]
Message-ID: <20031021174402.GA5692@sgi.com> (raw)
In-Reply-To: <3F6B7CCA.5040702@us.ibm.com>

I just tried -test8-mm1 on a 256p/128 node machine and these changes
almost work.  I still needed to change ZONE_SHIFT from BITS_PER_LONG - 8
to BITS_PER_LONG - 10 because of the way set_page_zone() is called from
memmap_init_zone() (set_page_zone(page, nid * MAX_NR_ZONES + zone);).
So shouldn't ZONE_SHIFT be BITS_PER_LONG -  NODES_SHIFT or something?

Jesse

On Fri, Sep 19, 2003 at 03:01:46PM -0700, Matthew Dobson wrote:
> Andrew,
> 	Here's a small update to the numnodes fix that went into -mm3.  The 
> biggest changes are:
> 	1) move the actual NODES_SHIFT and MAX_NUMNODES definitions into 
> linux/numa.h and include this in linux/mmzone.h, instead of being 
> directly in linux/mmzone.h.  This allows other files to include *just* 
> the NUMNODES stuff w/out grabbing all of mmzone.h.
> 	2) pull NODE_SHIFT out of linux/mm.h.  This isn't used anywhere in 
> 	the kernel, and it will only get confused with NODES_SHIFT.
> 	3) Fix the IA64 patch.  The original patch I had sent out hadn't 
> 	been tested on IA64.  It was mostly right, but there were circular 
> dependencies.  All better now, and acked by Jesse.
> 	4) In linux/mmzone.h, insert code to define MAX_NODES_SHIFT based on 
> the size of unsigned long.  For 64-bit arches, we can have a much larger 
> value.  This allows IA64 to have 100's or 1000's of nodes. 
> MAX_NODES_SHIFT is defined as 10 (ie: 1024 nodes) for 64-bit for now, 
> although it could likely be much larger.  For 32-bit it is 6 (ie: 64 nodes).
> 	5) Small cleanup in include/asm-arm/memory.h.  Mostly the result of 
> 	the new linux/numa.h file.  Much cleaner and more readable now.
> 
> Russell, if you get a chance, I'd really appreciate a sanity check on 
> the arm code.  It really hasn't been tested, but the changes are pretty 
> small.

  reply	other threads:[~2003-10-21 17:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 21:36 [PATCH] you have how many nodes?? Jesse Barnes
2003-09-10 22:12 ` Andrew Morton
2003-09-10 22:34   ` Jesse Barnes
2003-09-10 22:36     ` Andrew Morton
2003-09-10 23:46       ` Martin J. Bligh
2003-09-11  0:03         ` Jesse Barnes
2003-09-16  0:31           ` Matthew Dobson
2003-09-16  0:34             ` [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [1/5] Matthew Dobson
2003-09-16 12:43               ` Matthew Dobson
2003-09-16  0:35             ` [PATCH[ Clean up MAX_NR_NODES/NUMNODES/etc. [2/5] Matthew Dobson
2003-09-16  0:36             ` [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [3/5] Matthew Dobson
2003-09-16  0:37             ` [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [4/5] Matthew Dobson
2003-09-16  0:37             ` [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [5/5] Matthew Dobson
2003-09-16 16:47               ` Jesse Barnes
2003-09-19 22:01             ` [PATCH] you have how many nodes?? Matthew Dobson
2003-10-21 17:44               ` Jesse Barnes [this message]
2003-09-11  0:52   ` William Lee Irwin III

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=20031021174402.GA5692@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=akpm@osdl.org \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@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