From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] IA64 kexec-tools: memory_ranges arrays scalability issue
Date: Sat, 03 Feb 2007 03:24:58 +0000 [thread overview]
Message-ID: <20070203032457.GD3709@verge.net.au> (raw)
In-Reply-To: <45C3D89F.1060301@sgi.com>
On Fri, Feb 02, 2007 at 04:34:39PM -0800, Jay Lan wrote:
> There are two memory_ranges arrays declared in the IA64 kexec code.
> One in kexec-ia64.c and the other one in crashdump-ia64.c.
>
> They currently were allocated as a hard-coded size of array. Since
> SN systems may scale to hunders of nodes and each node may contain
> up to 12 DIMMs, the hard-coded size of 1024 is not enough for very
> large systems.
>
> The size of either array can not be greater than the number of
> entries in /proc/iomem, which is saved as "max_memory_ranges"
> and is used to dynamically allocate the two arrays.
>
>
> Signed-off-by: Jay Lan <jlan@sgi.com>
>
Thanks, applied.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
prev parent reply other threads:[~2007-02-03 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 0:34 [PATCH] IA64 kexec-tools: memory_ranges arrays scalability issue Jay Lan
2007-02-03 3:24 ` Horms [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=20070203032457.GD3709@verge.net.au \
--to=horms@verge.net.au \
--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