linux-kernel - Re: More thoughts on getting rid of ZONE

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]

Date:	Fri, 22 Sep 2006 17:23:54 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andi Kleen <ak@...e.de>
cc:	Martin Bligh <mbligh@...igh.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, akpm@...gle.com,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	James Bottomley <James.Bottomley@...eleye.com>,
	linux-mm@...ck.org
Subject: Re: More thoughts on getting rid of ZONE_DMA

On Sat, 23 Sep 2006, Andi Kleen wrote:

> The problem is that if someone has a workload with lots of pinned pages
> (e.g. lots of mlock) then the first 16MB might fill up completely and there 
> is no chance at all to free it because it's pinned

Ok. That may be a problem for i386. After the removal of the GFP_DMA 
and ZONE_DMA stuff it is then be possible to redefine ZONE_DMA (or 
whatever we may call it ZONE_RESERVE?) to an arbitrary size a the 
beginning of memory. Then alloc_pages_range() can dynamically decide to 
tap that pool if necessary. I already have checks for ZONE_DMA and 
ZONE_DMA32 in there. If we just rename those then what you wanted would 
be there. If additional memory pools are available then they
are used if the allocation restrictions fit to avoid a lengthy search.

This may mean that i386 and x86_64 will still have two zones. Its somewhat 
better.

However, on IA64 we would not need this since our DMA limit has been 
4GB in the past.

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