Often, a costly memory management is not necessary that can be repaired on reason of concatenations, for example. In this case, a simple memory management with a minimum af overhead of administration information is enough.
The here introduced Heap-manager requires with the administration from ≥64kB 3bytes up to 4GB 5bytes overhead per entry. Additional he can administer RAM and EE-PROM parallel and gives HW-indepenend tools for write accesses to the EE-PROM memory over the port.
Storage demand the pC/MEM V1.30a:
ROM: approximately 3 KByte (without MEM_Resize approximately 1kByte)
RAM: approximately 1 bytes per user (for MEM_GetErrno)
However, it are no MMU deposited mechanisms at present. Additional bytes would be needed per entry for MMU-depended data.
Sorry, I can't make this sources accessible because of overlaps with my job !
Small correction of MEM_Init. Complete code optimization and adaptations for porting to other hardware.
MEM_GetErrNo implemented. Small correction in MEM_Resize.
MEM_CleanUp implemented and integration of for that needed task-registration into the entries.
complete update to U08..U32 types.
Services of the pC/MEM version 1.30a (abbreviation)
This here presented function overview only serves as short overview.
For detailed information, you please look in Reference-Manual about pC/MEM.
Initialization of the Heap-Manager
Allocation of storage
release allocated storage
Size of allocated storage alters
on allocated EEPROM-heap write
allocated EEPROM-heap fill
release all allocated storage-elements of a task
Types of Memory: