 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
A simple memory pool module can allocate for example 3 pools at compile time with block sizes optimized for the application, which deploys the module. The application can allocate, access and free memory with the following interface:
I think this phrasing is a bit confusing. Compile-time allocation would mean to me that the memory is already allocated and defined at compile time, e.g. stack memory. A memory pool instead will usually work based on heap memory which is first allocated at runtime. Even if this allocation happens soon at the start of the programme this is something different than allocation at compile time to me. —Preceding unsigned comment added by 212.114.211.6 (talk) 10:36, 11 September 2007 (UTC)
Perhaps the Author is referring to global memory declared during compile time. —Preceding unsigned comment added by Adityazutshi (talk • contribs) 18:48, 25 October 2009 (UTC)
Memory pool vs malloc - benefits edit
The first point under benefits states (no fragmentation), but there does occur internal fragmentation. For instance, in case if the requested size doesn't exactly correspond to the blocksize.