On 14/08/20 17:10, Claudio Imbrenda wrote: > > The existing memory allocators are becoming more and more inadequate to > the needs of the upcoming unit tests (but also some existing ones, see > below). > > Some important features that are lacking: > * ability to perform a small physical page allocation with a big > alignment withtout wasting huge amounts of memory > * ability to allocate physical pages from specific pools/areaas (e.g. > below 16M, or 4G, etc) > * ability to reserve arbitrary pages (if free), removing them from the > free pool > > Some other features that are nice, but not so fundamental: > * no need for the generic allocator to keep track of metadata > (i.e. allocation size), this is now handled by the lower level > allocators > * coalescing small blocks into bigger ones, to allow contiguous memory > freed in small blocks in a random order to be used for large > allocations again I haven't reviewed the patches in detail, but the deficiencies of the page allocator are of course known and it's welcome that you're attempting to fix them! Thanks, Paolo
