Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pekka Enberg <penberg@...>
Cc: Alexey Dobriyan <adobriyan@...>, <linux-kernel@...>, <linux-mm@...>
Date: Tuesday, October 23, 2007 - 4:09 pm

On Tue, 23 Oct 2007, Pekka Enberg wrote:


The number of objects per page is reduced by enabling full debugging. That 
triggers a potential of more order 1 allocations but we are failing at 
order 0 allocs. slub_debug=F does not increase object size with debugging 
information but keeps things as they are while doing as much verification 
of slab integrity as possible.

One--potentially far fetched theory--is that the difference in alloc 
performance may trigger a race. But I guess it is more likely that we will 
find something wrong with the gfp flags (that I recategorized for 2.6.24).


-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Alexey Dobriyan, (Tue Oct 23, 2:16 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Tue Oct 23, 3:35 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Tue Oct 23, 4:09 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Wed Oct 24, 12:56 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Tue Oct 23, 3:57 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Wed Oct 24, 10:15 pm)
Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds), Christoph Lameter, (Wed Oct 24, 10:43 pm)