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: <d760cf2d0903181029r43bf417u502b46e08348f6ae@mail.gmail.com>
Date:	Wed, 18 Mar 2009 22:59:15 +0530
From:	Nitin Gupta <ngupta@...are.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3]: xvmalloc memory allocator

On Wed, Mar 18, 2009 at 10:28 PM, Christoph Lameter
<cl@...ux-foundation.org> wrote:
> On Wed, 18 Mar 2009, Nitin Gupta wrote:
>
>> > Slab memory is not backed by vmalloc space.
>> Oh, it uses "low memory". Still not good for compcache :)
>
> Only if you use 32 bit.
>

Yes, this point is for 32-bit only - many users were unhappy with
compcache size limit due to small vmalloc area on x86-32.

Nitin
--
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/