[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] fix memory management on efika/pegasos
From: |
Robert Millan |
Subject: |
Re: [PATCH] fix memory management on efika/pegasos |
Date: |
Thu, 4 Oct 2007 22:47:22 +0200 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Thu, Oct 04, 2007 at 01:38:55AM +0200, Marcin Kurek wrote:
> Hell[o]
>
> > What happens if you increase HEAP_MIN_SIZE ?
>
> Still fails I am affraid. I wonder is there any reason to use only
> first 4MB for heap ? I guess higer memory areas can be still accessed
> excluding 4-16 MB ?
>
> I attached my proposed patch to solve this problem. It tires to
> allocate 4MB heap at fixed position at 28MB (To avoid problems with
> relocation later on) and if it fails use the grub_available_iterate()
> as before. If should be used with ealier patch from this thread. I
> tested it on Pegasos 1 (Only one machine), Pegasos 2 (With few OF
> revisions starting from 2004 to 2006) and efika and it works quite
> well.
Doesn't sound correct to me. It seems like a workaround for a bug that we
don't know exactly what it is.
Why does it still fail if you increase HEAP_MIN_SIZE ? Is there any value
big enough that makes it work ? Does it still fail with the same error?
(not enough memory). Was _any_ region claimed at all by our code?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)