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:	Tue, 8 Jan 2008 17:50:54 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	akepner@....com
Cc:	Tony Luck <tony.luck@...el.com>,
	Grant Grundler <grundler@...isc-linux.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jes Sorensen <jes@....com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Roland Dreier <rdreier@...co.com>,
	James Bottomley <James.Bottomley@...eleye.com>,
	David Miller <davem@...emloft.net>,
	Muli Ben-Yehuda <muli@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC/PARTIAL PATCH 0/3] dma: passing "attributes" to dma_map_*
	routines

On Mon, Jan 07, 2008 at 06:32:22PM -0800, akepner@....com wrote:
> 
> The following patchset allows additional "attributes" to be 
> passed to dma_map_*/dma_unmap_* implementations. (The reason 
> why this is useful/necessary has been mentioned several times, 
> most recently here:
> http://marc.info/?l=linux-kernel&m=119258541412724&w=2.)
> 
> This is incomplete in that only ia64 and x86_64 are supported - 
> the purpose is mainly to give us something specific to discuss. 
> 
> The approach here is to change the dma_map_* interface so 
> that the last argument is an u32 which encodes the direction 
> of the dma and, optionally, other attributes. Changing the 
> interface is a bit intrusive, but callers of dma_map_* don't 
> need to be modified.

Onething I've missed with these patches is drivers actually using
it.  What driver actually needs it and why don't you send patches
for them?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ