Eric W. Biederman wrote:
>>(3) Contradicts (1) as well as issues with older kernels. Keep in mind what
>>happens if you violate this limit: the bootloader should be loading the initrd
>>as high as possible
> Hmm. Bootloaders have had lots of restrictions on getting up high.
> Plus in some real sense it make sense to pack the two as close
> together as possible. For 2.5.x and Al Viro's initfs work I'd like
> to do that.
> If you load your ramdisk at the same location every time, after
> a point you have fewer surprises, and potentially a simpler bootloader.
NO, PLEASE PLEASE PLEASE DON'T DO THAT!!!!
Not only would it royally fuck over people with small amounts of RAM, it
would also really fuck over people who use the Linux boot protocol for
other purposes, which is getting quite common.
>>, so the only difference is if you get the error message from
>>the boot loader or from the kernel later. If you're going to export a limit,
>>you better make sure it's right; "8MB except on low memory configurations"
>>doesn't cut it. It's exactly on those low memory configurations that this limit
>>matters *at all*.
> 8MB is the safe limit. The only worry some case right now is the
> bootmem allocator with a darn huge bitmap. It is allocated
> dynamically, and it is extremely hard to predict where that will be
> except in the initial page tables 8MB in size. If the ugly bitmap
> is allocated elsewhere the kernel can't use it.
"Safe limit" isn't applicable here. It either works or it doesn't.
You're breaking systems which it would otherwise work on, which is not
> So if we are going to fix the fragility please let's handle both ends.
> Then it will be o.k. to put the ramdisk where ever the kernel says
> it is safe. And we can stop this guessing and breaking game.
You're giving the boot loader options that are really inappropriate.
All that will do is result in more variance between boot loaders and the
resulting bugs that will bite some bootloaders and not others.
Allowing unneeded options in protocols is a source of bugs. You seem to
think this is a good idea, it's not.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:15 EST