From: Christoph Hellwig <hch@infradead.org>
To: Jack Steiner <steiner@sgi.com>
Cc: 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 08:57:35 +0000 [thread overview]
Message-ID: <20031106085735.A14360@infradead.org> (raw)
In-Reply-To: <20031105181911.GA22082@sgi.com>; from steiner@sgi.com on Wed, Nov 05, 2003 at 12:19:11PM -0600
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.
next prev parent reply other threads:[~2003-11-06 8:57 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 [this message]
2003-11-06 17:15 ` Jack Steiner
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=20031106085735.A14360@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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).