[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0943d9e0609070210p661a2cd6k5683d0956aaab5fe@mail.gmail.com>
Date: Thu, 7 Sep 2006 10:10:51 +0100
From: "Catalin Marinas" <catalin.marinas@...il.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10
On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
> On 07/09/06, Catalin Marinas <catalin.marinas@...il.com> wrote:
> > On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
> > > On 07/09/06, Catalin Marinas <catalin.marinas@...il.com> wrote:
> > > > On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
> > > > > CONFIG_DEBUG_MEMLEAK=y
> > > > > CONFIG_DEBUG_MEMLEAK_HASH_BITS=8
> >
> > Have you tried 16?
>
> No, I haven't.
8 hash bits would lead to a really slow hash table lookup since you
would only have 256 entries and it uses linked lists to deal with
collisions (you may have tens of thousands of pointers to be stored in
the hash). Anyway, I attach a patch which allows you to set small
values but it is highly unrecommended.
--
Catalin
View attachment "hash-bits-fix.patch" of type "text/x-patch" (1112 bytes)
Powered by blists - more mailing lists