On Thu, 15 Feb 2018, Matthew Wilcox wrote: > On Thu, Feb 15, 2018 at 09:49:00AM -0600, Christopher Lameter wrote: > > On Thu, 15 Feb 2018, Matthew Wilcox wrote: > > > > > What if ... on startup, slab allocated a MAX_ORDER page for itself. > > > It would then satisfy its own page allocation requests from this giant > > > page. If we start to run low on memory in the rest of the system, slab > > > can be induced to return some of it via its shrinker. If slab runs low > > > on memory, it tries to allocate another MAX_ORDER page for itself. > > > > The inducing of releasing memory back is not there but you can run SLUB > > with MAX_ORDER allocations by passing "slab_min_order=9" or so on bootup. > > Maybe we should try this patch in order to automatically scale the slub > page size with the amount of memory in the machine? Well setting slub_min_order may cause allocation failures. You would leave that at 0 for a prod configuration. Setting slub_max_order higher would work. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
