On Sat, 10 Mar 2007, Andrew Morton wrote:
> Is this safe to think about applying yet?
Its safe. By default kernels will be build with SLAB. SLUB becomes only a
selectable alternative. It should not become the primary slab until we
know that its really superior overall and have thoroughly
Is this safe to think about applying yet?
We lost the leak detector feature.
It might be nice to create synonyms for PageActive, PageReferenced and
PageError, to make things clearer in the slub core. At the expense of
making things less clear globally. Am unsure.
-
To unsubscribe from this
[PATCH] SLUB The unqueued slab allocator v4
V4->V5:
- Single object slabs only for slabs > slub_max_order otherwise generate
sufficient objects to avoid frequent use of the page allocator. This is
necessary to compensate for fragmentation caused by frequent uses of
the page allocator. We
[PATCH] SLUB The unqueued slab allocator v4
V4-V5:
- Single object slabs only for slabs slub_max_order otherwise generate
sufficient objects to avoid frequent use of the page allocator. This is
necessary to compensate for fragmentation caused by frequent uses of
the page allocator. We
Is this safe to think about applying yet?
We lost the leak detector feature.
It might be nice to create synonyms for PageActive, PageReferenced and
PageError, to make things clearer in the slub core. At the expense of
making things less clear globally. Am unsure.
-
To unsubscribe from this
On Sat, 10 Mar 2007, Andrew Morton wrote:
Is this safe to think about applying yet?
Its safe. By default kernels will be build with SLAB. SLUB becomes only a
selectable alternative. It should not become the primary slab until we
know that its really superior overall and have thoroughly tested
6 matches
Mail list logo
