[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
problem with memory allocation
- Date: Tue, 03 Aug 1999 09:08:19 -0700
- From: gumby at zembu.com (D. V. Henkel-Wallace)
- Subject: problem with memory allocation
At 11:03 03-08-99 -0500, joel at OARcorp.com wrote:
>On Tue, 3 Aug 1999, D. V. Henkel-Wallace wrote:
> > At 10:26 03-08-99 -0500, joel at oarcorp.com wrote:
> > >malloc is built on top of Region which is built on top of a Heap.
> > Does anybody on this list actually take advantage of this layering?
>I will actually go so far as to say that virtually no one has ever had
>multiple regions in the same application.
>The only cases I can think of are where the second region was used to
>manage some special purpose memory.
Yes, this is the only case I can imagine; in fact your example is really a
special-case of it.
So what I really should have asked: could we just collapse this
stacking...perhaps eliding regions?
Does orkid require it? And if so, does that matter any more?
> > Everybody who uses malloc or new uses the same single region. I can
> > understand wanting to use different regions for some applications, but
> > different heaps?
>Logically, a region is just an RTEMS SuperCore heap with optional blocking
>There are always two SuperCore heaps in an application -- the executive
>workspace (directly a SuperCore heap) and the C program heap (a region
>which is built on top of a SuperCore heap).
>The layering is:
> + Ada or C++ new
> + C Heap (malloc)
> + Region
> + SuperCore Heap
> + Executive Workspace
> + SuperCoreHeap