All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@SGI.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Jes Sorensen <jes@trained-monkey.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, jbarnes@SGI.com,
	torvalds@osdl.org
Subject: Re: [patch] increse MAX_NR_MEMBLKS to same as MAX_NUMNODES on NUMA
Date: Mon, 19 Jan 2004 16:45:35 -0600	[thread overview]
Message-ID: <20040119224535.GA12728@sgi.com> (raw)
In-Reply-To: <4990000.1074542883@[10.10.2.4]>

On Mon, Jan 19, 2004 at 12:08:04PM -0800, Martin J. Bligh wrote:
> > Since we now support # of CPUs > BITS_PER_LONG with cpumask_t it would
> > be nice to be able to support more than BITS_PER_LONG memory blocks.
> 
> Nothing uses them. We're probably better off just removing them altogether.

I dont understand.
node_memblk[] is used on IA64 in arch/ia64/mm/discontig.c (& other places too).


-- 
Thanks

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



  reply	other threads:[~2004-01-19 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 13:05 [patch] increse MAX_NR_MEMBLKS to same as MAX_NUMNODES on NUMA Jes Sorensen
2004-01-19 20:08 ` Martin J. Bligh
2004-01-19 22:45   ` Jack Steiner [this message]
2004-01-20  2:24     ` Jesse Barnes
2004-01-20  3:12       ` Jack Steiner
2004-01-20  6:25         ` Martin J. Bligh
2004-01-20 10:59           ` Jes Sorensen
2004-01-20 16:11             ` Martin J. Bligh
2004-01-22 15:24               ` Jes Sorensen
2004-01-23  6:09                 ` Martin J. Bligh
2004-01-20  5:21       ` Martin J. Bligh

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=20040119224535.GA12728@sgi.com \
    --to=steiner@sgi.com \
    --cc=akpm@osdl.org \
    --cc=jbarnes@SGI.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.