public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: akepner@sgi.com
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: linux-kernel@vger.kernel.org, Roland Dreier <rdreier@cisco.com>,
	glebn@voltaire.com
Subject: Re: [RFC/PATCH] allow memory to be tagged "coherent" via dma_map_sg()
Date: Tue, 17 Jul 2007 08:22:44 -0700	[thread overview]
Message-ID: <20070717152244.GI16538@sgi.com> (raw)
In-Reply-To: <20070717101658.GB18721@rhun.ibm.com>

On Tue, Jul 17, 2007 at 01:16:58PM +0300, Muli Ben-Yehuda wrote:
> On Mon, Jul 16, 2007 at 07:18:12PM -0700, akepner@sgi.com wrote:
> .....
> > --- a/include/linux/dma-mapping.h
> > +++ b/include/linux/dma-mapping.h
> > @@ -95,4 +95,11 @@ static inline void dmam_release_declared_memory(struct device *dev)
> >  }
> >  #endif /* ARCH_HAS_DMA_DECLARE_COHERENT_MEMORY */
> >  
> > +#ifndef ARCH_DOES_POSTED_DMA
> > +static inline int
> > +dma_data_direction_set_dmaflush(enum dma_data_direction dir, int dmaflush) {
> > +	return (dir);
> > +}
> > +#endif /* ARCH_DOES_POSTED_DMA */
> > +
> >  #endif
> 
> The generic bits look much better than the previous version,
> thanks. Is the generic dma_data_direction_set_dmaflush really needed?

Yes, dma_data_direction_set_dmaflush is used in ib_umem_get() to pass 
the additional bit down to sn_dma_map_sg(). 

> if yes, what about dma_data_direction_get_direction and
> dma_data_direction_get_dmaflush?
> 

The dma_data_direction_get_* functions are used only in sn2-arch-
specific code (sn_dma_map_sg()), so they don't need to be defined 
for other architectures.

-- 
Arthur


      reply	other threads:[~2007-07-17 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  2:18 [RFC/PATCH] allow memory to be tagged "coherent" via dma_map_sg() akepner
2007-07-17 10:16 ` Muli Ben-Yehuda
2007-07-17 15:22   ` akepner [this message]

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=20070717152244.GI16538@sgi.com \
    --to=akepner@sgi.com \
    --cc=glebn@voltaire.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.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