VM_AREA size

What would the ramifications be of increasing VM_AREA size in include/asm-i386/page.h from 128mb to 256mb. What would be the proper way to increase this if the above isn't?

Quoted 3 lines · Mark Hounschell

What would the ramifications be of increasing VM_AREA size in include/asm-i386/page.h from 128mb to 256mb. What would be the proper way to increase this if the above isn't?

I think you mean __VMALLOC_RESERVE? For the most part it's straightforward to bump it up. _However_, that breaks boot loader assumptions about where to load initrd, causing mayhem in that case (and initramfs?). That's second hand info: if I'm wrong or out-of-date, Peter is the authority and will correct me; or try Google VMALLOC_RESERVE boot.

Quoted 6 lines · Hugh Dickins

Quoted 3 lines · Mark Hounschell

What would the ramifications be of increasing VM_AREA size in include/asm-i386/page.h from 128mb to 256mb. What would be the proper way to increase this if the above isn't?

Quoted 6 lines

I think you mean __VMALLOC_RESERVE? For the most part it's straightforward to bump it up. _However_, that breaks boot loader assumptions about where to load initrd, causing mayhem in that case (and initramfs?). That's second hand info: if I'm wrong or out-of-date, Peter is the authority and will correct me; or try Google VMALLOC_RESERVE boot.

I think it affects initramfs too.

It only affects boot loaders which don't support version 2.03 of the boot protocol; unfortunately that includes GRUB last I checked.

We really need a better dialog with the GRUB people, unfortunately at least I have unsuccessful in starting such a dialog.

GRUB, in particular, needs to report the boot loader ID they're using, plus support version 2.03 of the protocol.

-hpa