public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akepner@sgi.com
Cc: grundler@parisc-linux.org, jbarnes@virtuousgeek.org, jes@sgi.com,
	randy.dunlap@oracle.com, rdreier@cisco.com,
	James.Bottomley@steeleye.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] allow drivers to flush in-flight DMA v2
Date: Fri, 28 Sep 2007 15:43:39 -0700 (PDT)	[thread overview]
Message-ID: <20070928.154339.02281405.davem@davemloft.net> (raw)
In-Reply-To: <20070928010926.GM30013@sgi.com>

From: akepner@sgi.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'.

  reply	other threads:[~2007-09-28 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  1:09 [PATCH 0/4] allow drivers to flush in-flight DMA v2 akepner
2007-09-28 22:43 ` David Miller [this message]
2007-10-03  1:04   ` akepner
2007-10-03 17:10     ` Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070928.154339.02281405.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@steeleye.com \
    --cc=akepner@sgi.com \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox