lkml.org 
[lkml]   [2006]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10
On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> I get a kernel panic
> http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/panic.jpg
>
> http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/kml-config

Well, you set CONFIG_DEBUG_MEMLEAK_HASH_BITS to 32, this means that
kmemleak needs to allocate (sizeof(void*) * 2^32) which is 16GB of
RAM. I think a maximum of 20 should be enough (I got acceptable
results with 16 hash bits, the default value, and it seemed to do
better with 18).

--
Catalin
-
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: 2006-09-07 10:07    [W:0.101 / U:0.740 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site