Message-ID: <40059CAD.FE57825E@compro.net>
Date: Wed, 14 Jan 2004 14:46:53 -0500
From: Mark Hounschell <markh@compro.net>
Reply-To: markh@compro.net
Organization: Compro Computer Svcs.
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: VM_AREA size
References: <Pine.LNX.4.44.0401141827330.1711-100000@localhost.localdomain> <4005912F.9020008@zytor.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1424
Lines: 37

"H. Peter Anvin" wrote:
> 
> Hugh Dickins wrote:
> > On Wed, 14 Jan 2004, Mark Hounschell wrote:
> >
> >>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.
> >
> 
> 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

Thanks guys. I "was" using grub I guess it's now back to lilo.

Mark
-
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/