linux-kernel - Re: [PATCH] [8/13] Enable the mask allocator for x86

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: <Pine.LNX.4.64.0803101011530.24069@schroedinger.engr.sgi.com>
Date:	Mon, 10 Mar 2008 10:13:49 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] [8/13] Enable the mask allocator for x86

On Sat, 8 Mar 2008, Andi Kleen wrote:

> What sparsemem reference do you mean?

Its just the use of MAX_DMA_ADDRESS in mm/sparse-vmemmap.c

> But the ZONE_DMA32 actually makes sense, but changing the semantics
> under such a large driver base isn't a good idea. 

The driver base can only be the x86_64 only device drivers since the zone 
is not used by any other architectures. That is fairly small AFAICT.

> It depends on the requirements of the bootmem user.  Some do need
> memory <4GB, some do not. The mask allocator itself is a client in fact
> and it requires low memory of course.

The point is that it would be good to relocate as much memory allocated at 
boot as possible beyond 4GB.

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