Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757441Ab0G2PNF (ORCPT ); Thu, 29 Jul 2010 11:13:05 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:41079 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754344Ab0G2PND (ORCPT ); Thu, 29 Jul 2010 11:13:03 -0400 Message-ID: <4C519A6E.8000002@cs.helsinki.fi> Date: Thu, 29 Jul 2010 18:12:46 +0300 From: Pekka Enberg User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Daniel J Blueman CC: Catalin Marinas , Linux Kernel Subject: Re: [2.6.35-rc6 patch] increase kmemleak robustness at boot References: <4C505F86.7050509@cs.helsinki.fi> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 828 Lines: 17 Daniel J Blueman wrote: >> I would rather change the static early alloc buffer with something >> like bootmem allocation (the recursiveness should be bound, kmemleak >> tracks bootmem allocations as well). But I'm on holiday until middle >> of August and not able to do any tests in this area. > > Indeed, moving to dynamic early allocation is all the more better. For > now, I'll increase the early allocation to 15200 elements, as the > 400-entry buffer wraps 38. If it's just kmemleak_init() we're talking about, slab caches are up at that point so you can just use kmalloc(). -- 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/