This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Memory allocation

Hello,
I want to allocate a memory in a memory pool, so I call "init_mempool" function like this:

init_mempool (&XBYTE[0x0400], 0x0C00);

How can I know that the memory pool doesn't overlay on other vars in xdata? if it overlay, when I call "malloc" function, does it destroy other xdata vars? Another question : can I call init_mempool 2 times in my program?

Parents

0 Andy Neil over 19 years ago in reply to Andy Neil
How about:
#define HEAP_SIZE 0x0C00 U8 heap[HEAP_SIZE]; init_mempool( heap, HEAP_SIZE );
But doesn't this shown the fallacy of the whole idea? You have to define the heap size at compile-time anyway, so why bother with dynamic allocation at all?!
Cancel
Vote up 0 Vote down

Cancel

Reply

0 Andy Neil over 19 years ago in reply to Andy Neil
How about:
#define HEAP_SIZE 0x0C00 U8 heap[HEAP_SIZE]; init_mempool( heap, HEAP_SIZE );
But doesn't this shown the fallacy of the whole idea? You have to define the heap size at compile-time anyway, so why bother with dynamic allocation at all?!
Cancel
Vote up 0 Vote down

Cancel

Children

0 erik malund over 19 years ago in reply to Andy Neil

mempool ....
the '51 ain't no PC

how few do realize that?

Erik
Cancel
Vote up 0 Vote down

Cancel
0 Andy Neil over 19 years ago in reply to erik malund

"the '51 ain't no PC"

For a PC Application, the author doesn't know how much memory will be available when it actually gets run by the customer on the cusomer's equipment - so dynamic allocation makes sense.
(same applies to other Computer systems)

On an embedded system (especially 8051-based), the amount of memory usually is known at compile time - so dynamic allocation makes little sense (especially on an 8051-based system, where resources are generally limited).
Cancel
Vote up 0 Vote down

Cancel