Thread (33 messages) 33 messages, 6 authors, 2006-05-23

Re: [PATCH 5/6] Have ia64 use add_active_range() and free_area_init_nodes

From: Andy Whitcroft <hidden>
Date: 2006-05-19 14:24:50
Also in: linux-mm, lkml

Mel Gorman wrote:
On Sun, 14 May 2006, Andrew Morton wrote:
quoted
Mel Gorman [off-list ref] wrote:
quoted
Size zones and holes in an architecture independent manner for ia64.
This one makes my ia64 die very early in boot.   The trace is pretty
useless.

config at http://www.zip.com.au/~akpm/linux/patches/stuff/config-ia64
An indirect fix for this has been set out with a patchset with the
subject "[PATCH 0/2] Fixes for node alignment and flatmem assumptions" .
For arch-independent-zone-sizing, the issue was that FLATMEM assumes
that NODE_DATA(0)->node_start_pfn == 0. This is not the case with
arch-independent-zone-sizing and IA64. With
arch-independent-zone-sizing, a nodes node_start_pfn will be at the
first valid PFN.
quoted
<log snipped>

Note the misaligned pfns.
You will still get the message about misaligned PFNs on IA64. This is
because the lowest zone starts at the lowest available PFN which may not
be 0 or any other aligned number. It shouldn't make a different - or at
least I couldn't cause any problems.
With the updates I sent out to the zone alignment checks yesterday this
should now be ignored correctly without comment.  The first zone is
allowed to be misaligned because we expect alignment of the mem_map.
With bob picco's patch from your set we ensure it is so.

-apw
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help