From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - Increase max number of nodes (cpu_to_node_map)
Date: Thu, 06 Nov 2003 17:06:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106813866603928@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106806288024897@msgid-missing>
On Wed, Nov 05, 2003 at 01:44:17PM -0600, Jack Steiner wrote:
> I hit a problem with systems having > 256 nodes. The
> cpu_to_node_map array is an array of char - needs to be
> bigger.
>
> Here is a patch that changes it to a short.
shouldn't that be an unsigned short so we don't run into problems
when adding the 32769th processor?
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-11-06 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 19:44 [PATCH] - Increase max number of nodes (cpu_to_node_map) Jack Steiner
2003-11-06 17:06 ` Matthew Wilcox [this message]
2003-11-06 17:43 ` 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=marc-linux-ia64-106813866603928@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@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