linux-kernel - Re: 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]

Message-Id: <200609221206.57701.jesse.barnes@intel.com>
Date:	Fri, 22 Sep 2006 12:06:57 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Christoph Lameter <clameter@....com>
Cc:	Martin Bligh <mbligh@...igh.org>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, Rohit Seth <rohitseth@...gle.com>
Subject: Re: ZONE_DMA

On Friday, September 22, 2006 11:40 am, Christoph Lameter wrote:
> On Fri, 22 Sep 2006, Jesse Barnes wrote:
> > Right, the internals are arch specific and don't necessarily have to
> > rely on a zone, depending on their DMA constraints.
>
> From what I can see the arch specific do some tricks and then pick
> GFP_DMA or something to get memory that is appropriately limited. Having
> the ability to retrieve pages from a certain range from the page
> allocator would fix this issue and improve the ability of devices to
> allocate memory.

Right, being able to allocate from specific ranges would obviate the need 
for GFP_DMA and the various zones.  It would come with a cost though since 
the VM would have to become aware of pressure at various ranges rather 
than just on zones like we have now.  I think that's where things get 
tricky.

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