On 17/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:> Hi Catalin,>> On 17/08/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:> > On 13/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:> > > It's kmemleak 0.9 issue. I have tested kmemleak 0.8 on 2.6.18-rc1and> > > 2.6.18-rc2. I haven't seen this before.> >> > it looks like it was caused by commit> > fc818301a8a39fedd7f0a71f878f29130c72193d where free_block() now calls> > slab_destroy() with l3->list_lock held.>> I'll revert this commit.>> >> > The prio_tree use (which doesn't alloc memory) instead of the> > radix_tree is about 4 times slower when scanning the memory and I> > don't think I'll use it.> >> > It leaves me with the options of either implementing my own memory> > allocator based on pages

[MODSLAB 7/7] A slab allocator: Page Slab allocator"The page slab is a specialized slab allocator that can only handlepage order size object. It directly uses the page allocator totrack the objects and can therefore avoid the overhead of theslabifier."http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/3023.html