* Ingo Molnar <mingo@elte.hu> wrote:

quoted text
> [...] increasing SECTION_SIZE_BITS in include/asm-x86/sparsemem.h from 
> 26 to 27 makes it go away. (i.e. we use section chunks of 128 MB 
> instead of 64 MB before) [...]

btw., here's the 'good' versus 'bad' bootup log (vanilla kernel spiced 
with a few extra stats printed out [*]):

 http://redhat.com/~mingo/misc/boot.26.log         # bad
 http://redhat.com/~mingo/misc/boot.27.log         # good

the only difference is SECTION_SIZE_BITS == 26 versus 27.

looking at the dmesg diff, there's just minimal (and expected) offset 
difference in some structure sizes. (more sparse maps use a bit more 
memory)

	Ingo

[*] in case you wonder why memory_section->map is twice its size - i 
    doubled it just to eliminate any doubts about off-by-one errors. 
    Their natural size, as returned by bootmem, was 512KB plus 16 bytes 
    (!), which seemed a bit weird. Probably a section entry came between 
    two memory map allocations?
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/