[Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem

Daniel Phillips d.phillips at partner.samsung.com
Wed Jun 11 19:26:49 UTC 2014

On 06/11/2014 12:03 PM, Christoph Lameter wrote:
> Well this is likely to be a bit of a hot subject but I have been thinking
> about this for a couple of years now. This is just a loose collection of
> some concerns that I see mostly at the high end but many of these also are
> valid for more embedded solutions that have performance issues as well
> because the devices are low powered (Android?).
> There are numerous issues in memory management that create a level of
> complexity that suggests a rewrite would at some point be beneficial:
> 1. The need to use larger order pages, and the resulting problems with
> fragmentation. Memory sizes grow and therefore the number of page structs
> where state has to be maintained. Maybe there is something different? If
> we use hugepages then we have 511 useless page structs. Some apps need
> linear memory where we have trouble and are creating numerous memory
> allocators (recently the new bootmem allocator and CMA. Plus lots of
> specialized allocators in various subsystems).

mem_map should be a radix tree?



More information about the Ksummit-discuss mailing list