[okl4-developer] OKL4 v2.1: About memory layout
Frank Kaiser
frank.kaiser at opensynergy.com
Wed Sep 24 20:27:52 EST 2008
Hello, David
See below.
Regards
Frank
> -----Original Message-----
> From: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org]
On Behalf
> Of David Given
> Sent: Tuesday, September 23, 2008 5:51 PM
> To: developer at okl4.org
> Subject: Re: [okl4-developer] OKL4 v2.1: About memory layout
>
> Frank Kaiser wrote:
> [...]
> > The conclusion is that the memory allocation algorithm carried out
be
> > the GNU loader under control of the ELF Adorn and ELF Weaver tools
is
> > somewhat unpredictable, and I do not see why the manipulation of the
> > heap size has such a significant effect.
>
> Alignment issues, perhaps? If it knows your platform supports, say,
4kB,
> 64kB and 1MB pages (like some ARM platforms), it might be trying to
move
> stuff around in order to fit everything into the smallest number of
> pages; that'll increase performance.
That is my guess, too, that it has something to do with page alignment,
but the observed behaviour with respect to the heap size value just does
not fit. And Malcolm's mail has not really given an explanation.
>
> You say it's a NOR flash device --- are you using XIP?
No, since the XIP configuration is broke: it only makes the kernel code
executable from flash; Iguana, driver and application code still has to
be copied into RAM for execution.
>
> --
> David Given
> dg at cowlark.com
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
More information about the Developer
mailing list