linux-kernel - Re: [PATCH 1/4] compcache: 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.DEB.1.10.0908261209240.9933@gentwo.org>
Date:	Wed, 26 Aug 2009 12:10:24 -0400 (EDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Nitin Gupta <ngupta@...are.org>
cc:	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Pekka Enberg <penberg@...helsinki.fi>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-mm-cc@...top.org
Subject: Re: [PATCH 1/4] compcache: xvmalloc memory allocator

On Wed, 26 Aug 2009, Nitin Gupta wrote:

> I went crazy. I meant 40 bits for PFN -- not 48. This 40-bit PFN should be
> sufficient for all archs. For archs where 40 + PAGE_SHIFT < MAX_PHYSMEM_BITS
> ramzswap will just issue a compiler error.

How about restricting the xvmalloc memory allocator to 32 bit? If I
understand correctly xvmalloc main use in on 32 bit in order to be
able to use HIGHMEM?

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