linux-kernel - Re: [PATCH 2/3]: xvmalloc memory allocator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0903171237180.21582@qirst.com>
Date:	Tue, 17 Mar 2009 12:41:09 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Nitin Gupta <ngupta@...are.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3]: xvmalloc memory allocator

On Tue, 17 Mar 2009, Nitin Gupta wrote:

> Slub allocator could not be used due to fragmentation issues:
> http://code.google.com/p/compcache/wiki/AllocatorsComparison
> Data here shows kmalloc using ~43% more memory than TLSF and xvMalloc
> is showed ~2% more space efficiency than TLSF (due to smaller metadata).

Well this looks like the use of 2^n sizes of the kmalloc arrayse cause a
lot of wastage here. Creating slab caches that fit your needs may help?
Have you had a look at the SLOB approach?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/