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

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, 28 Sep 2007 15:43:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akepner@....com
Cc:	grundler@...isc-linux.org, jbarnes@...tuousgeek.org, jes@....com,
	randy.dunlap@...cle.com, rdreier@...co.com,
	James.Bottomley@...eleye.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] allow drivers to flush in-flight DMA v2

From: akepner@....com
Date: Thu, 27 Sep 2007 18:09:26 -0700

> 
> On Altix, DMA may be reordered between a device and host memory. 
> This reordering can happen in the NUMA interconnect, and it usually 
> results in correct operation and improved performance. In some 
> situations it may be necessary to explicitly synchronize DMA from 
> the device.
> 
> This patchset allows a memory region to be mapped with a "dmabarrier". 
> Writes to the memory region will cause in-flight DMA to be flushed, 
> providing a mechanism to order DMA from a device.

My only beef with this patch set is that it seems
a bit much to create a totally new function name every
time we want to set some kind of new attribute on some
DMA object.  Why not add a "dma_set_flags()" or similar
that can be used later on to set other kinds of aspects
we'd like to change?

You can make the arguments "u32 flags" and "int dir".
Actually you should probably use the dma direction
enumaration instead of 'int'.
-
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/