Re: [patch 2/5] slub: Fallback to kmalloc_large for failing higher order allocs

["Pekka Enberg" <penberg@cs.helsinki.fi>]

[Sorry for the duplicate. My email client started trimming cc's...]

On Thu, Feb 14, 2008 at 6:02 AM, Christoph Lameter <clameter@sgi.com> wrote:
> Slub already has two ways of allocating an object. One is via its own
>  logic and the other is via the call to kmalloc_large to hand of object
>  allocation to the page allocator. kmalloc_large is typically used
>  for objects >= PAGE_SIZE.
>
>  We can use that handoff to avoid failing if a higher order kmalloc slab
>  allocation cannot be satisfied by the page allocator. If we reach the
>  out of memory path then simply try a kmalloc_large(). kfree() can
>  already handle the case of an object that was allocated via the page
>  allocator and so this will work just fine (apart from object
>  accounting...).

Sorry, I didn't follow the discussion close enough. Why are we doing
this? Is it fixing some real bug I am not aware of?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>