#15 fixed memory size allocation

[Joe]

Hello Richard,

I would propose a feature which would be very helpfull reducing memory fragmentation, increasing speed during memory allocation and ease the message passing framework implementation.

So, as many other RTOS provide such a feature, it would be very good to implement a fixed memory size allocating/freeing mechanism for task-level and interrupt-level handling.

I hope You and many other FreeRTOS-users agree to my feature request and you will decide to add it to the next revisions of FreeRTOS.

regards

Joe

[Richard]

Logged In: YES
user_id=1056745
Originator: NO

Thaks for your feedback.

Actually, original versions of FreeRTOS.org used a memory pool implementation, but this was removed as many users found tuning the memory pools to be efficient for their application too difficult. If you go back to *very* old versions (still available in SourceForge) you will find this. You could add this code as a heap_4.c implementation, if you do this and send it to me I could include it in the download.

Regards.

[Joe]

Logged In: YES
user_id=1545418
Originator: YES

Hi Richard,

I am not sure which module you mean, but I found a porthead.c-module, is it the right one ?
B.t.w. I am dreaming of a module where I can create several memory-partitions as e.g. where I am able to specify the size and the number of usable blocks. The allocation routine may take an unused block of the certain partition and may be the free-routine knows implicit the used partition. If you are interested in my proposal i can specify such an interface ?

regards

Joe

[Dmitriy A. Cherepanov]

Logged In: YES
user_id=1940836
Originator: NO

May be I would suggest you an improved alghoritm of heap.c If you would approve my current suggestions

[Richard Barry]

Memory allocation is part of the port layer so users can create their own - plus the memory allocation schemes have been expanded and enhanced since this ticket was created.