linux-kernel - [PATCH 0/4] allow drivers to flush in-flight DMA

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-next>] [day] [month] [year] [list]

Message-ID: <20070925235843.GK30013@sgi.com>
Date:	Tue, 25 Sep 2007 16:58:43 -0700
From:	akepner@....com
To:	Grant Grundler <grundler@...isc-linux.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jes Sorensen <jes@....com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	David Miller <davem@...emloft.net>,
	Roland Dreier <rdreier@...co.com>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/4] allow drivers to flush in-flight DMA



This is a followup to http://lkml.org/lkml/2007/8/24/280

Despite Grant's desire for a more elegant solution, there's 
not much new here. I moved the API change from pci.h to 
dma-mapping.h and removed the pci_ prefix from the name. 

Problem Description
-------------------
On Altix, DMA may be reordered within the NUMA interconnect.
This can be a problem with Infiniband, where DMA to Completion Queues 
allocated in user-space can race with data DMA. This patchset allows 
a driver to associate a user-space memory region with a "dmaflush" 
attribute, so that writes to the memory region flush in-flight DMA, 
preventing the CQ/data race.

There are four patches in this set:

  [1/4] dma: add dma_flags_set_dmaflush() to dma interface
  [2/4] dma: redefine dma_flags_set_dmaflush() for sn-ia64
  [3/4] dma: document dma_flags_set_dmaflush()
  [4/4] mthca: allow setting "dmaflush" attribute on user-allocated memory

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