All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Kill dma_is_consistent()
Date: Thu, 23 Nov 2006 16:06:17 +0000	[thread overview]
Message-ID: <20061123160617.GC8984@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1164297574.2829.9.camel@mulgrave.il.steeleye.com>

On Thu, Nov 23, 2006 at 09:59:33AM -0600, James Bottomley wrote:
> On Thu, 2006-11-23 at 15:03 +0000, Ralf Baechle wrote:
> > dma_is_consistent() is ill-designed in that it does not have a struct device
> > argument which makes proper support for systems that consist of a mix of
> > coherent and non-coherent DMA devices hard.
> 
> At the time the interface was designed, the general consensus was that
> it was easier to recognise incoherent memory regions by their address
> range than by which device they came from.  The main proponent of this
> being arm, if I remember rightly.

I don't remember that being particularly discussed, and it seems that
no one has implemented it (but possibly implemented their own stuff
in arch private code.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2006-11-23 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 15:03 [PATCH] Kill dma_is_consistent() Ralf Baechle
2006-11-23 15:59 ` James Bottomley
2006-11-23 16:06   ` Russell King [this message]
2006-11-23 17:24   ` [PATCH] Add struct dev pointer to dma_is_consistent() Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2006-11-23 15:04 [PATCH] Kill dma_is_consistent() Ralf Baechle

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=20061123160617.GC8984@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.