Hi,

On Sat, 29 Mar 2008, Christoph Lameter wrote:
quoted text
>  > Yes it uses its own logic if the object is managed by SLUB but not if the
>  > object is too big and/or the allocation forwarded to the page allocator
>  > or for other internal allocations of buffers etc.

On Sat, Mar 29, 2008 at 11:29 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
quoted text
>  Wrong.
>
>  It uses it's own logic for __GFP_ZERO *regardless* of size.

Christoph, I think you're overlooking the same thing I was until Linus
straightened me out. We're calling kmalloc_large() from __slab_alloc()
for the fall-back case which causes a bug fixed by Linus' revert.

On Sat, Mar 29, 2008 at 11:29 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
quoted text
>  You don't have a f*cking clue about this cocde that you're supposed to be
>  maintaining, do you?

Yeah, me too. Fortunately we have you as our upstream maintainer :-).

                        Pekka
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/