diff options
| author | Jay Lan <jlan@sgi.com> | 2007-02-02 16:34:39 -0800 |
|---|---|---|
| committer | Simon Horman <horms@verge.net.au> | 2007-02-03 12:23:31 +0900 |
| commit | 49c5c5b662774e91ecebd95e4f7650e6567a6624 (patch) | |
| tree | 0f93f8d76cb5a95b55fc1fb1928d4d11991479ab /kexec/kexec.c | |
| parent | 02e6bd686d64abd747e17c268dc1b913e14b5c91 (diff) | |
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 <jlan@sgi.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'kexec/kexec.c')
0 files changed, 0 insertions, 0 deletions