SLUB: CONFIG_LARGE_ALLOCS must consider MAX_ORDER limit
authorChristoph Lameter <clameter@sgi.com>
Tue, 15 May 2007 08:42:06 +0000 (01:42 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Tue, 15 May 2007 15:54:01 +0000 (08:54 -0700)
commitcfbf07f2a80b618c42a42c20d83647ea8fcceca0
tree575c9834d1ed69459c79162042647008f2097123
parent6a3ee3d5529c5e66aedf91401bfac65c61998639
SLUB: CONFIG_LARGE_ALLOCS must consider MAX_ORDER limit

Take MAX_ORDER into consideration when determining KMALLOC_SHIFT_HIGH.
Otherwise we may run into a situation where we attempt to create general
slabs larger than MAX_ORDER.

Signed-off-by: Christoph Lameter <clameter@sgi.com>
Cc: "David S. Miller" <davem@davemloft.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/slub_def.h