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: <Pine.LNX.4.64.0609221129170.8356@schroedinger.engr.sgi.com>
Date:	Fri, 22 Sep 2006 11:32:28 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Jesse Barnes <jesse.barnes@...el.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 Fri, 22 Sep 2006, Jesse Barnes wrote:

> Oh, it's already there in the tree, but obviously some drivers still need 
> to be converted.  See Documentation/DMA-API.txt.  It's not PCI specific 
> like the old PCI DMA interface (Documentation/DMA-mapping.txt) and 
> provides a way for drivers to specify their addressing limitations 
> (dma_supported and dma_set_mask), which allows the underlying architecture 
> code to report a failure if necessary.

AFAICT this is dealing with special dma issues and not with the problem of 
allocating memory for a certain supported address range from the page 
allocator. From the first glance at the docs it looks as if it is relying 
on __GFP_DMAxx to get the allocations right. I think the code could be 
changed though to call a new page allocator function to get the right 
memory and that would work for all devices using that API.

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