public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: Christoph Hellwig <hch@infradead.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, davidm@hpl.hp.com,
	jbarnes@sgi.com
Subject: Re: [PATCH] - Allow architectures to increase size of MAX_NR_MEMBLKS
Date: Thu, 6 Nov 2003 11:15:17 -0600	[thread overview]
Message-ID: <20031106171517.GA11600@sgi.com> (raw)
In-Reply-To: <20031106085735.A14360@infradead.org>

On Thu, Nov 06, 2003 at 08:57:35AM +0000, Christoph Hellwig wrote:
> On Wed, Nov 05, 2003 at 12:19:11PM -0600, Jack Steiner wrote:
> > This fixes a problem that occurs on system with >64 nodes. 
> > 
> > Previously, MAX_NR_MEMBLKS was defined as BITS_PER_LONG. This
> > patch allows an architecture to override this definition by
> > defining a value in the arch-specific asm-xxx/mmzone.h file.
> 
> IMHO this is too much clutter.  Just make it mandatory for the
> architectures to define their own MAX_NR_MEMBLKS in the numa case.
> 
> Or actually even better just have a 
> 
> #ifndef MAX_NR_MEMBLKS
> #define MAX_NR_MEMBLKS	1
> #endif
> 
> in the generic code and let every architecture that wants to override
> it do so.


I like this idea but wanted to minimize risk to other architectures 
at this point in 2.6.

AFAICT, the only other achitecture that would require change would 
be i386. I'm not familar with the i386 numa architecture. It
looks like the change would be to add the definition of
MAX_NR_MEMBLKS to include/asm-i386/numaq.h.

What is the value of MAX_NR_MEMBLKS for NUMAQ? 

Are any architectures affected that I am overlooking???

I'm ok with either approach. What do other think??


-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



      reply	other threads:[~2003-11-06 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 18:19 [PATCH] - Allow architectures to increase size of MAX_NR_MEMBLKS Jack Steiner
2003-11-06  8:57 ` Christoph Hellwig
2003-11-06 17:15   ` Jack Steiner [this message]

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=20031106171517.GA11600@sgi.com \
    --to=steiner@sgi.com \
    --cc=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=hch@infradead.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