public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>, Jesse Barnes <jbarnes@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] you have how many nodes??
Date: Wed, 10 Sep 2003 16:46:40 -0700	[thread overview]
Message-ID: <41000000.1063237600@flay> (raw)
In-Reply-To: <20030910153601.36219ed8.akpm@osdl.org>

>> > I think.  We could just say "dang numaq needs five bits", so:
>> > 
>> > 
>> > 	# if BITS_PER_LONG == 32
>> > 	# define ZONE_SHIFT 5
>> > 	# else
>> > 	# define ZONE_SHIFT 10
>> > 	# endif
>> 
>> That's fine with me, do you want me to rediff and send a new patch?
> 
> Well your patch as it stands would appear to break NUMAQ builds, due to
> NUMAQ setting MAX_NUMNODES directly in the arch code.  ia64 is using
> another layer of macroification via NR_NODES instead.
> 
> MAX_NUMNODES, NR_NODES and MAX_NR_NODES appear to be a bit of a mess, and
> they should all be replaced with shift distances anyway.

;-)

Yes, it's a turgid mess.

I'd prefer to define things in terms of MAX_NUMNODES, and derive the shifts
from that if possible - much more intuitive to maintain.
But other than that I agree completely with you.
 
> Could you please get together with Martin Bligh, come up with something
> which works on NUMAQ and your 128 CPU PDA and also cast an eye across the
> other architectures (sparc64, sh, ...)?  It all needs a bit of thought and
> a spring clean.

I'll have a look, I'm sure we can come up with something between us.

M.


  reply	other threads:[~2003-09-10 23:57 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 [this message]
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
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=41000000.1063237600@flay \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=jbarnes@sgi.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