linux-kernel - Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction

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: <20061209222117.a2bb64a1.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Sat, 9 Dec 2006 22:21:17 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, clameter@...r.sgi.com,
	apw@...dowen.org, akpm@...l.org
Subject: Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [0/4] introduction

On Sat, 9 Dec 2006 12:51:37 +0100
Heiko Carstens <heiko.carstens@...ibm.com> wrote:

> > Virtual mem_map is not useful for 32bit archs. This uses huge virtual
> > address range.
> 
> Why? The s390 vmem_map implementation which I sent last week to linux-mm
> is merged in the meantime. It supports both 32 and 64 bit.
> The main reason is to keep things simple and avoid #ifdef hell.
> 
> Since the maximum size of the virtual array is  about 16MB it's not much
> waste of address space. Actually I just changed the size of the vmalloc
> area, so that the maximum supported physical amount of memory is still 1920MB.

I'm sorry. I don't stop anyone who want to use vmem_map.
(My brain is polluted by ugly x86 36bit-space/32bit arch.)

-Kame

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