IA64 kexec-tools: memory_ranges arrays scalability issue

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 <jlansgi.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 <jlansgi.com>
> 

Thanks, applied.


-- 
Horms
  H: http://www.vergenet.n
et/~horms/
  W: http://www.valinux.co.jp
/en/

-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html