LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: akepner@sgi.com
Cc: Tony Luck <tony.luck@intel.com>,
	Grant Grundler <grundler@parisc-linux.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Jes Sorensen <jes@sgi.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Roland Dreier <rdreier@cisco.com>,
	David Miller <davem@davemloft.net>,
	Muli Ben-Yehuda <muli@il.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dma/ia64: update ia64 machvecs
Date: Wed, 30 Jan 2008 11:25:58 -0600	[thread overview]
Message-ID: <1201713958.3292.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20080130055212.GT30022@sgi.com>

In general, the patches look reasonable to me.  Just an observation:

On Tue, 2008-01-29 at 21:52 -0800, akepner@sgi.com wrote:
> diff --git a/include/linux/dma-attrs.h b/include/linux/dma-attrs.h
> index e69de29..31af292 100644
> --- a/include/linux/dma-attrs.h
> +++ b/include/linux/dma-attrs.h
> @@ -0,0 +1,48 @@
> +#ifndef _DMA_ATTR_H
> +#define _DMA_ATTR_H
> +#ifdef ARCH_USES_DMA_ATTRS
> +
> +enum dma_attr {
> +       DMA_ATTR_BARRIER,
> +       DMA_ATTR_FOO,
> +       DMA_ATTR_GOO,
> +       DMA_ATTR_MAX,
> +};
> +


The attribute names (DMA_ATTR_...) are going to have to live somewhere
outside of the #ifdef ARCH_USES_DMA_ATTRS otherwise we'll get compile
failures of drivers using attributes on architectures that don't support
them.

Secondly, DMA_ATTR_BARRIER doesn't quite sound right.  What you're
actually doing is trying to prescribe strict ordering, so shouldn't this
be something like DMA_ATTR_STRICT_ORDERING (and perhaps with a
corresponding DMA_ATTR_RELAXED_ORDERING for the PCIe case).  also,
strike the DMA_ATTR_FOO and DMA_ATTR_GOO since they have no plausible
meaning.

James



  reply	other threads:[~2008-01-30 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  5:52 akepner
2008-01-30 17:25 ` James Bottomley [this message]
2008-01-30 19:45   ` akepner

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=1201713958.3292.27.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akepner@sgi.com \
    --cc=davem@davemloft.net \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=randy.dunlap@oracle.com \
    --cc=rdreier@cisco.com \
    --cc=tony.luck@intel.com \
    --subject='Re: [PATCH 2/4] dma/ia64: update ia64 machvecs' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).