https://bugzilla.novell.com/show_bug.cgi?id=254316 ------- Comment #3 from andrea@novell.com 2007-03-14 18:48 MST ------- Good point, I didn't notice this ramdisk_max parameter in the 2.03 header. grub is using it. moveto = (moveto - len) & 0xfffff000; max_addr = (lh->header == LINUX_MAGIC_SIGNATURE && lh->version >= 0x0203 ? lh->initrd_addr_max : LINUX_INITRD_MAX_ADDRESS); if (moveto + len >= max_addr) moveto = (max_addr - len) & 0xfffff000; So ok, kernel is certainly partly to blame for this 512M thing. But I don't think the right solution is to move the initrd lower. If you move it down, either by lowering ramdisk_max or by making grub smarter, you risk fragmenting memory during the bootmem allocator allocations that may leave partial pages unused. so it would waste a bit of memory, not a big deal but if we're going to change something, we better do it optimal. Loading initrd at the end of the normal zone sounds right. So I think we either have to raise ramddisk_max to 800M or to relocate the initrd manually before initializing the bootmem allocator (the latter sounds a bit safer as it won't clash so easily if you enlarge the vmalloc space). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.