lkml.org 
[lkml]   [2007]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)
On Tue, 23 Oct 2007, Pekka Enberg wrote:

> On 10/23/07, Christoph Lameter <clameter@sgi.com> wrote:
> > Not sure what this is. Maybe the slowing SLUB solves the race.
>
> What kind of race are you thinking of? What I initially thought was
> that the problem is that SLUB messes up some other VM heuristics due
> to different object sizes, not holding on to empty slabs, and/or page
> allocator pass-through. I guess only object size is affected by
> debugging, though?

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).


-
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/

\
 
 \ /
  Last update: 2007-10-23 22:11    [W:2.353 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site