On 07/09/06, Catalin Marinas <[email protected]> wrote:
On 07/09/06, Michal Piotrowski <[email protected]> wrote:
> On 07/09/06, Catalin Marinas <[email protected]> wrote:
> > Have you tried 16?
>
> No, I haven't.
With DEBUG_MEMLEAK_HASH_BITS=16 system woks fine.
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.
How about documeting maxial "safe" values?
Something like
"If you have X MB/GB of RAM memory you can set Y
X | Y
256 MB | 25
512 MB | 26
1GB | 27
2GB | 28
4GB | 29"
--
Catalin
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
